unevaluated* updates (and some annotation dependency cleanup) #1541
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
13 tasks
gregsdennis
changed the title
jviotti
reviewed
Oct 13, 2024
jviotti
approved these changes
Oct 13, 2024
jdesrosiers
approved these changes
Oct 14, 2024
karenetheridge
requested changes
Oct 14, 2024
| [in-place applicators](#in-place) defined in this document. | ||
|
|
||
| This keyword applies its subschema to any array elements which have not been | ||
| deemed "evaluated" per {{#unevaluated}}. Validation passes if the keyword's |
There was a problem hiding this comment.
How is {{#unevaluated}} parsed/replaced here?
There was a problem hiding this comment.
I believe it's replaced with the section title and a link to the section.
@jdesrosiers can confirm.
Co-authored-by: Karen Etheridge <[email protected]>
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.
What kind of change does this PR introduce?
Updates for spec release
Issue & Discussion References
Summary
Updates the
unevaluated*keywords and sections that reference them (e.g. "this keyword's annotation affects the behavior of this other keyword").Does this PR introduce a breaking change?