Interpretations docs update #6
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
zprobst
reviewed
Apr 18, 2024
docs/reference/interpreting.md
Outdated
Comment on lines
373
to
374
|
|
||
| ### Source Node and Relationship Interpretation Combined |
There was a problem hiding this comment.
Can we move this section after Switch so that it is not buried in the docs for the Value Providers?
zprobst
approved these changes
Apr 18, 2024
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.
This document update is for the new
allow_createflag that was added to source node interpretation.Also documents the interaction between SourceNodeInterpretation and RelationshipNodeInterpretation as it pertains to
source.allow_createandrelationship.node_creation_rule.Also includes a Developer Reference for Interpreting.