-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Parameter naming leads to error #4908
Comments
Many thanks for raising this bug report @svenho. 🐛 We will now attempt to reproduce the bug based on the steps you have provided. Please ensure that you've provided the necessary information for a minimal reproduction, including but not limited to:
If you have a support agreement with Neo4j, please link this GitHub issue to a new or existing Zendesk ticket. Thanks again! 🙏 |
This is caused by our This can be solved by sorting the arguments by name length, so we make sure to always replace longer params ( |
Fix parameters replace logic #4908
Describe the bug
This error occured first with @neo4j/graphql v4.4.6 and is still present in v5.2.0.
I experienced the bug within cypher FOREACH loops but probably it is not restricted to this.
It seems to be an issue with the naming of the parameters:
workProjectDetails
containsworkProject
at the beginning.(I can workaround this issue by renaming
workProjectDetails
tox_workProjectDetails
.)Reproduction
I habe a mutation like this (abbreviated):
Now I call the mutation like this (in Apollo studio):
Then I get an error like this:
It's interesting that the parameter within the error appears as
NULLDetails
.System:
The text was updated successfully, but these errors were encountered: