Provides a way to provide custom handling for unknown parameters in ReflectiveConfigGroup #3027
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
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.
If a ConfigGroup based on ReflectiveConfigGroup has to add an unmapped parameter, usually an exception is thrown.
In some cases, it could make sense to provide special handling in such cases, e.g. to implement backward compatibility to older parameter names, to support a migration from older to newer parameters, etc.
This PR adds two methods
handleAddUnknownParam(...)andhandleGetUnknownValue(...)(matchingaddParam(...)andgetValue(...)) that are designed to be overwritten. The default implementation reuses the existing logic in ReflectiveConfigGroup. Custom config groups can overwrite the methods and add custom functionality to deal with unknown parameters.Fixes #2960