Feat/#22 support multi module architecture #26
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…reamline factory retrieval logic
…er metadata with error handling
…ity and consistency
…nt uri matching logic
…ing registry explicitly
…oute mapping correctness
angryPodo
added
the
FEAT✨
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR enables multi-module support by implementing the ServiceLoader pattern.
Previously, the processor generated a duplicate WispRegistry class for every module, causing build errors. Now, it generates unique WispModuleRegistry_{Hash} classes and automatically registers them via META-INF/services.
Changes:
Tested with the sample app.
Closes: #22