Change visibility of ConfigEntryBase constructor to internal protected to allow for external implementations
#403
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.
Description
I added
protectedto the access modifiers for theConfigEntryBaseconstructorMotivation and Context
This allows for an external assembly to create a type that extends off of
ConfigEntryBaseCurrently, the only constructor is
internal, which prevents an external assembly from creating a class that derives from itHow Has This Been Tested?
I built the project in both debug and release mode.
I replaced the existing
BepInEx.Core.dllin my install with a new oneEverything seemed normal
Screenshots (if appropriate):
Types of changes
Checklist: