- 
                Notifications
    You must be signed in to change notification settings 
- Fork 35
Add errors for unsupported combinations with path modes #399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
| This PR includes documentation updates New pages: Updated pages: | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @dogofbrian. I added some comments.
| @@ -1,7 +1,7 @@ | |||
| = 42I39 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| = 42I39 | |
| :page-role: new-2025.11 | |
| = 42I39 | 
| @@ -0,0 +1,11 @@ | |||
| = 42N60 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| = 42N60 | |
| :page-role: new-2025.11 | |
| = 42N60 | 
| @@ -0,0 +1,11 @@ | |||
| = 42N61 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| = 42N61 | |
| :page-role: new-2025.11 | |
| = 42N61 | 
|  | ||
| == Status description | ||
| error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors or explicit match modes is not allowed. | ||
| error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors, explicit match modes or explicit path modes is not allowed. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors, explicit match modes or explicit path modes is not allowed. | |
| error: syntax error or access rule violation - invalid use of shortest path function. Mixing the `{ <<fun>> }` function with path selectors, explicit match modes, or explicit path modes is not allowed. | 
| = 42N60 | ||
|  | ||
| == Status description | ||
| error: syntax error or access rule violation - unsupported combination of match mode and path mode. REPEATABLE ELEMENTS with `{ <<pathMode>> }` path mode is not supported. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is REPEATABLE ELEMENTS capitalized?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we also add an explanation/ example scenario for each of the errors? See 22N71, 22N69, 22NAB, 42I64, and many more for inspiration.
| = 42N61 | ||
|  | ||
| == Status description | ||
| error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing `{ <<pathModeList>> }` in the same graph pattern is not supported. Split the pattern into separate MATCH clauses instead. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing `{ <<pathModeList>> }` in the same graph pattern is not supported. Split the pattern into separate MATCH clauses instead. | |
| error: syntax error or access rule violation - unsupported mixing of different path modes. Mixing `{ <<pathModeList>> }` in the same graph pattern is not supported. Split the pattern into separate `MATCH` clauses instead. | 
New error codes (and one message update) for path mode semantic checking