Add chain invocation for $moduleInit()
, $moduleStart()
, and $configureInit()
methods
#42387
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
During the codegen phase we generate a set of functions for initializing modules and their ballerina constructs. As of now, these initializations are done using a flattened dependency list for each ballerina module.
Fixes #42367
Approach
Changed the
$moduleInit()
and$moduleStart()
BIRFunction generation boilerplate to generate a invocations of$moduleInit()
functions instead of<.init>()
functions. The new method generation will be as follows,Did the same change for generated
$configureInit()
methods inside$configurationMapper
class.Samples
Full change samples can be found in this document.
Remarks
Check List