-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
Context
Today, there is no easy way to check if a Concerto JSON AST is valid. When running concerto print, we get back a CTO string with errors. We should add a validateAST command and/or validate on print.
Expected Behavior
New concerto validate-ast command
and/or
concerto print should throw an error when given an invalid AST as input
Steps to Reproduce
- Create an invalid JSON AST (eg. use invalid values for enum options)
- Run
concerto printon that AST - See invalid CTO as output
Existing issues
Context
Your Environment
- Version used:
- Environment name and version (e.g. Chrome 39, node.js 5.4):
- Operating System and version (desktop or mobile):
- Link to your project:
Metadata
Metadata
Assignees
Labels
No labels