-
Notifications
You must be signed in to change notification settings - Fork 22
Closed
Description
Start implementations with creating standardized AST via stampit specification and continue with transformer of CST -> AST. This will allows us to continue using current babel/graphql inspired traversal mechanism of ours. I'd need to change an architecture of code to reflect the possibility to plug a custom CST -> AST transformers if somebody would like to create a competing implementation using ANTLR4 or other parser generator.
This is direct follow up of https://github.com/swagger-api/oss-planning/issues/132
- implement CST -> AST transformer
- implement error accumulation mechanism
- replace json-ast for tree-sitter
- remove comments support
- error handling
- browser version of build fragments (web-tree-sitter)
- buildable ApiDOM demo build from linking current monorepo
packages