Serialising a double inverse property path results in a syntactically invalid query #165
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
|
@MPvHarmelen I just had a glance at the files changed and there is only a commit adding the test file; did you forget to commit the actual code changes? I'm not a maintainer so I can't run the workflow to see if the tests are currently failing or not. |
|
Sorry, no! I encountered this issue and wanted to create an issue/pull-request combination to improve the DX for debugging the problem, but I forgot the issue half of it... |
|
(Quickly rebased this one to trigger CI.) |
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.
When serialising the following query, the surrounding
()are forgotten, causing a syntactically invalid query to be generated:becomes:
which is syntactically invalid.
This pull-request contains a failing test for this case.