feat: Add support for specifying custom controls on config properties#252
Open
BlayTheNinth wants to merge 2 commits into
Open
feat: Add support for specifying custom controls on config properties#252BlayTheNinth wants to merge 2 commits into
BlayTheNinth wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Custom controls are registered via
BalmCustomConfigControlRegistrarand then referenced through their identifier in the config property. For annotation-based configs,@CustomControl("identifier")can be used.Supports native config provider widget classes or
AbstractWidget, which will be wrapped.Validation configured within the config control only applies to the screen control and only in providers that support it, not to the underlying config.