Safely escape relation type, fix create and delete relation methods #24
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.
While testing the
mcp-neo4j-memory
with Claude, I ran into issues creating and deleting relations with the errormeaning
$(relation.relationType)
was being used directly in the Cypher query rather than substituting the value.This pull request creates a
_safe_relation_type
method to sanitize the relationship type, and then uses string interpolation to form the query with the sanitized relation type. This methodology is used for both thecreate_relations
anddelete_relations
method.