Reset Static Variable for Module Creation #1982
Merged
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.
Hi,
In this pull request, I address an issue that occurs when creating a new module (not the first module). Since the list of modules is stored in a static variable during execution, the newly created module’s files are not immediately recognized. This creates problems when subsequent commands are called, such as:
To resolve this, I reset the static variable used for storing the module list. This ensures the module paths are re-scanned, allowing the new module to be fully recognized and enabling the commands to work correctly.
Fixes #1956