Improve documentation for the yaml.schemas setting#1184
Merged
datho7561 merged 1 commit intoredhat-developer:mainfrom Dec 19, 2025
Merged
Improve documentation for the yaml.schemas setting#1184datho7561 merged 1 commit intoredhat-developer:mainfrom
yaml.schemas setting#1184datho7561 merged 1 commit intoredhat-developer:mainfrom
Conversation
Fixes redhat-developer#1147 Signed-off-by: David Thompson <davthomp@redhat.com>
Contributor
Author
|
@TMA-2 @shin19991207 if you have some time, could you let me know if the new wording of the documentation makes more sense? |
Member
|
@datho7561 Looks good to me. Thanks, David. |
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
2 participants
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.
What does this PR do?
Improves the documentation for the
yaml.schemassetting by specifying that the expected value is a string-to-string map, where the keys represent schema locations and the values are globs for the files that the schema applies to.What issues does this PR fix or reference?
Fixes #1147
Is it tested? How?
It's a documentation change, so I'll ask a couple people if it makes sense.