-
Notifications
You must be signed in to change notification settings - Fork 11
Makes the semantic analysis work with partial queries #519
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
Conversation
🦋 Changeset detectedLatest commit: 7fcb568 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Nice improvements! Only change I see that we need is to add a changeset.
Also, I was thinking it might be nice to link the PR where the actual changes happen in the main repo. That one is private however, so I wonder if we're still allowed to add a URL here?
@@ -337,7 +337,7 @@ describe('Semantic validation spec', () => { | |||
]); | |||
}); | |||
|
|||
test('Does not trigger semantic errors when there are syntactic errors', () => { | |||
test('Does not trigger semantic errors when there are irrecoverable syntactic errors', () => { |
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.
What is the difference between an "irrecoverable" syntactic error and a "recoverable" one?
Im thinking something like "The semantic analysis is always run now, but when parsing the query breaks so early that antlr doesnt see the later clauses for what they are, there's nothing to analyze"?
In this case - parsing breaks on metch, and we never parse n and m as variables
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.
As I explained in a call: irrecoverable syntactic errors are those that would not produce any AST whatsoever
What
Makes it possible to run the transpiled semantic analysis on unfinished queries:
Before we were getting only syntax errors on queries like:

Now:

How
It updates the semantic analysis artifacts that have already been modified to run the semantic analysis even if the AST would generate a null.