Skip to content

Output nodes should be per subschema not per keyword #1249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gregsdennis merged 13 commits into from
Aug 28, 2022
Merged

Output nodes should be per subschema not per keyword #1249

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
91fea47
Move contains to "other" applicator section
jdesrosiers Apr 20, 2021
a469d9b
updated output structure description, example schema and instances, a…
gregsdennis Jun 27, 2022
8a73d7b
update wording for structures and associated examples
gregsdennis Jun 27, 2022
b4ff06e
removed 'detailed' format; added annotations examples; some rewording…
gregsdennis Jun 27, 2022
997bed9
updated description of nested results
gregsdennis Jun 29, 2022
e1344cc
use actual generated output for the examples
gregsdennis Jun 30, 2022
742221a
fix URIs and remove location props from root node on basic
gregsdennis Jul 1, 2022
0d7b836
edits suggested by @handrews
gregsdennis Jul 27, 2022
fe67355
using 'dereferenced evaluation structure
gregsdennis Aug 4, 2022
509ed28
more verbiage tweaks to output
gregsdennis Aug 4, 2022
b6799cd
correcting the number of output formats
gregsdennis Aug 4, 2022
843a683
update example locations for evaluationPath and schemaLocation
gregsdennis Aug 5, 2022
b6ea8a3
add clarification around empty-string error messages
gregsdennis Aug 14, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading