-
Notifications
You must be signed in to change notification settings - Fork 5
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
Parse error for queries is not specific enough #231
Comments
You can test it on pipeline https://github.com/kbss-cvut/s-pipes/blob/54dfb128d59584980a78be036965ab089d164dfa/doc/examples/hello-world/hello-world.sms.ttl#L53C1-L53C1 as follows:
|
Closed
Another queries (validation queries) can be tested here |
blcham
added a commit
that referenced
this issue
Jul 5, 2024
blcham
added a commit
that referenced
this issue
Jul 5, 2024
MSattrtand
pushed a commit
that referenced
this issue
Jul 14, 2024
blcham
pushed a commit
that referenced
this issue
Jul 15, 2024
blcham
pushed a commit
that referenced
this issue
Jul 15, 2024
blcham
pushed a commit
that referenced
this issue
Jul 15, 2024
blcham
pushed a commit
that referenced
this issue
Jul 17, 2024
blcham
pushed a commit
that referenced
this issue
Jul 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a module such as ApplyConstruct, when it fails due to a parse error, it says something like:
The issue is that I am not able to find out why the parse error occurred, as I do not see the original query. The query should be logged as well (or maybe even pointing somehow to where the error exactly occurs so the user does not necessarily need to use an external editor to find it out from the line/column number).
A/C:
The text was updated successfully, but these errors were encountered: