Let jsonld handle value nodes/Literal for context search #2750
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.
If jsonld parser is set from version 1.0 to 1.1 it looses the ability to handle value nodes that are set as
@type
for an object. This change should only make the parser ignore value nodes when searching for an already found context. Thus the ability to handle those is not lost, when setting the parser version to 1.1This behaviour is not expected of the jsonld parser. Other parsers will fail, when a
@type
is given a literal.Necessary change to set the default version of the parser to 1.1, because roundtrip test fails otherwise
Background discussion to this change is #2747. (Issue #2606 is the reason for this change.)
Summary of changes
in jsonld-contexts ignore dicts(value nodes), when searching for a context
No changes in tests or documentation, because this is not an expected behaviour.
Checklist
the same change.
so maintainers can fix minor issues and keep your PR up to date.