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
Currently, when the TypeScript transformer encounters a node it does not understand, we just throw an Error and display the syntax (text) that could not be processed. This is not too big of a deal when running tsc, but it kills the language server when editing in VS code.
Instead, the transformer should not throw and instead output a NullLiteral or ErrorNode to the AST.
For errors, we will rely on a language service plugin (see: #10) to add domain-specific diagnostics instead of throwing an error.
The text was updated successfully, but these errors were encountered:
Currently, when the TypeScript transformer encounters a node it does not understand, we just throw an Error and display the syntax (text) that could not be processed. This is not too big of a deal when running
tsc
, but it kills the language server when editing in VS code.Instead, the transformer should not throw and instead output a
NullLiteral
orErrorNode
to the AST.For errors, we will rely on a language service plugin (see: #10) to add domain-specific diagnostics instead of throwing an error.
The text was updated successfully, but these errors were encountered: