Properties to accept Literal. QueryBuilder.set to accept Literal in data #99
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
|
Also, for some context, I'm intending to use this to set properties using a variable from earlier parts of my cypher query (UNWIND and WITH). The proposed changes could introduce the risk of cypher injections. I'm circumventing this by using a Variable class that extends Literal in my project and including sanitisation checks. |
added 2 commits
June 7, 2024 10:20
|
@chingmunn I see, thanks for the info! If you think that neogma can benefit from the Variable class being built-in, let me know. PRs are always welcome too! I published this to v1.14.1 |
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.
No description provided.