Generate custom JSON schema for dynamic setting#9632
Merged
charliermarsh merged 1 commit intomainfrom Jan 24, 2024
Merged
Conversation
Member
Author
|
Oh actually, I was able to test it with https://www.jsonschemavalidator.net/. Valid integer: Valid string: Invalid string: |
cf30214 to
bdb6e11
Compare
bdb6e11 to
eb3bf31
Compare
Member
Author
|
No prob! |
Contributor
|
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
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.



Summary
If you paste in the TOML for our default configuration (from the docs), it's rejected by our JSON Schema:
It seems like the issue is with:
Specifically, since that value uses a custom Serde implementation, I guess Schemars bails out? This PR adds a custom representation to allow
"dynamic"(but no other strings):This seems like it should work but I don't have a great way to test it.
Closes #9630.