Detect blank nodes from frontend #1160
Merged
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
Merged
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.
Since PR #1151 (v0.6.0), the VOID endpoint doesn't return blank nodes for containers. When no blank nodes are indicated for a React-Admin resource, it now automatically search blank nodes 2-levels deep.
If you know the blank nodes you want (or don't want), you should use the
blankNodesproperty, either as afilterprop of the List or on the data model. This will increase the performances of the SPARQL query.If you want to change the depth of the blank nodes automatic detection, you can also set
blankNodesDepth(on thefilterprop of the List or on the [data model]), which defaults to2.blankNodesDepth: 0is equivalent toblankNodes: []