fix: throw Error instead of raw array for TypeScript compilation fail…#162
Open
nikhiltelkar2005-glitch wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes an issue in
TemplateMarkToJavaScriptCompiler.compile()where a rawArray<CompilerError>was being thrown instead of a standardErrorobject when a template formula contained invalid TypeScript.Previously, any caller catching this compilation failure would receive
[object Object]without a.messageproperty or a stack trace, making the rich error information (collected by twoslash) completely inaccessible.Changes Made
Errorobject..messageto be human-readable, exposing the exact:Related Issues
Fixes #128
(Note:
TemplateArchiveProcessorhas a similar issue whereresult.errorsis not checked after compilation, which will be addressed in a follow-up issue).