Changes utilities.py:to_cypher_value to utilize double quotes when …

[james-geiger]

…creating cypher values.

Description

This PR alters the to_cypher_values function to utilize double quotes when serializing into a cypher query.

Pull request type

Please delete options that are not relevant.

• Bugfix

Related issues

Delete section if this PR doesn't resolve any issues.

Closes #318

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

######################################

Reviewer checklist (the reviewer checks this part)

• Core feature implementation
• Tests
• Code documentation
• Documentation on gqlalchemy/docs

######################################

[antejavor]

It looks good, since it improves consistent in string quotes

[katarinasupe]

Hi @james-geiger, I see there are other tests that should be fixed accordingly. Also, let me see if I understood correctly:

The problem you're resolving here is the case of having a single apostrophe in a string. A current approach in GQLAlchemy uses a single apostrophe around the string in the Cypher query. That is not a good approach when a string has a single apostrophe. A solution to this issue is to have double quotes around a string in Cypher that allows a single apostrophe when needed. This PR doesn't include any changes related to the \n issue mentioned.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ james-geiger
❌ katarinasupe
_{You have signed the CLA already but the status is still pending? Let us recheck it.}