Increase visibility of RegistrationBuilder and InjectorCache to make VContainer more extensible. #564
Conversation
This file contains 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
This will allow users to create project specific registration and tailor VContainer to their own needs.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I too have been having problems with extensibility lately. Thanks. |
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.
With members of
RegistrationBuilderbeinginternal, it's very difficult to create your own project-specific registrations.I increased visiblity of members inside
RegistrationBuildertoprotected internal. This should allow classes that inherit fromRegistrationBuilderto have access to those fields.I also changed the visibility of
InjectorCachetopublic. This is needed for the cases that a customRegistrationBuilderneeds to be made.