Add unsafeEscapeOptions - Cherry Pick from 5 LTS #6046
Merged
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.
(cherry picked from commit 660861a)
Description
Add
unsafeEscapeOptions
toNeo4jGraphQL
features with the following flags:disableRelationshipTypeEscaping
(default tofalse
)disableNodeLabelEscaping
(defaults tofalse
)These flags remove the automatic escaping of node labels and relationship types in the generated Cypher.
For example, given the following schema:
A GraphQL query going through the
actors
relationship:Will normally generate the following Cypher for the relationship:
The label
ACTED IN
is escaped by placing it inside backticks (```), as some characters in it are susceptible of code injection.If the option
disableRelationshipTypeEscaping
is set inNeo4jGraphQL
, this safety mechanism will be disabled:Generating the following (incorrect) Cypher instead:
This can be useful in very custom scenarios where the Cypher needs to be tweaked or if the labels and types have already been escaped.