We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
expand-manifest.jsonld#tc037
jq '.sequence[] | select(."@id" == "#tc037")' tests/expand-manifest.jsonld
which gives:
{ "@id": "#tc037", "@type": [ "jld:PositiveEvaluationTest", "jld:ExpandTest" ], "name": "property-scoped contexts which are alias of @nest", "purpose": "Nesting terms may have property-scoped contexts defined.", "input": "expand/c037-in.jsonld", "expect": "expand/c037-out.jsonld", "option": { "specVersion": "json-ld-1.1" } }
cat tests/$(jq -r '.sequence[] | select(."@id" == "#tc037") | .input' tests/expand-manifest.jsonld) | jq
that gives
{ "@context": { "@version": 1.1, "@vocab": "http://example.org/", "nest": { "@id": "@nest", "@context": { "@vocab": "http://example.org/nest/" } } }, "nest": { "property": "should be in /nest" } }
cat tests/$(jq -r '.sequence[] | select(."@id" == "#tc037") | .expect' tests/expand-manifest.jsonld) | jq
which gives
[ { "http://example.org/nest/property": [ { "@value": "should be in /nest" } ] } ]
[ { "http://example.org/property": [ { "@value": "should be in /nest" } ] } ]
+ "http://example.org/nest/property": [ - "http://example.org/property": [
My understanding of @nest logic is insufficient to judge who's right here. Any thoughts?
@nest
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Manifest
jq '.sequence[] | select(."@id" == "#tc037")' tests/expand-manifest.jsonld
which gives:
Input
that gives
Expected output
which gives
What about the JSON-LD Playground?
Difference
Question
My understanding of
@nest
logic is insufficient to judge who's right here. Any thoughts?The text was updated successfully, but these errors were encountered: