Support Ranges & Integer Validation In Config Schemas #10118
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.
↪️ Pull Request
Adds support for config schemas with ranges & integer restrictions.
Closes #10117
💻 Examples
Example usage:
this restricts the
quality
parameter to be an integer in the range of 1-100, and it will fail with an error if it is not.🚨 Test instructions
I did not add any tests for it because there wasn't really any existing tests for the config schema stuff.
Testing it manually should be quite easy, just make a config schema with a restriction on the range or a restriction to only integers, and then make a config which violates that restriction.
✔️ PR Todo