Add validation rules to disable nullable elements in a list, when used inside @node
or @relationshipProperties
.
#5837
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.
As the title, this PR adds a validation rule to avoid a list of nullable elements present in the
@node
or@relationshipProperties
types as they are not natively supported in Neo4j.Test: 3905.test.ts is skipped as
@cypher
fields with non-@node
target are currently not implemented in the 7.x branch