You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.
Adding location data to nodes in the AST would allow for 'possibly' new languages to be built using the AST as a target (stage 2 of my master plan, think SASS for SQL 😉 ). (This is similar to how ES6 -> ES5 transpilers work, and indeed Java, Scala, etc).
The parser in this case could be thought of as a reference spec for an SQL AST.
The text was updated successfully, but these errors were encountered:
I'd like to use the parser as basis for a linter. But without location data, there is no way of knowing where a certain AST element originated in the query.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Adding location data to nodes in the AST would allow for 'possibly' new languages to be built using the AST as a target (stage 2 of my master plan, think SASS for SQL 😉 ). (This is similar to how ES6 -> ES5 transpilers work, and indeed Java, Scala, etc).
The parser in this case could be thought of as a reference spec for an SQL AST.
The text was updated successfully, but these errors were encountered: