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
JS comments are being parsed by the plugin, and if the plugin finds invalid syntax, it throws errors. This is common in our codebase when people write example usages of a component invocation, and it even catches on some JSDoc comments. really, any JS comment with {{ will attempt to be parsed by the plugin.
example: this JSDoc comment with a type annotation containing an object, which looks like a double-curly template invocation:
/**
* Error message from loading the suggestions and whether the user can retry.
* @type {{ errorMessage: string, canRetry: boolean} | undefined }}
*/
JS comments are being parsed by the plugin, and if the plugin finds invalid syntax, it throws errors. This is common in our codebase when people write example usages of a component invocation, and it even catches on some JSDoc comments. really, any JS comment with
{{
will attempt to be parsed by the plugin.example: this JSDoc comment with a type annotation containing an object, which looks like a double-curly template invocation:
this breaks the prettier plugin
something about the double-curly in the comment block is throwing off prettier, because when i delete that line it works fine
recommendation: just don't parse the contents of JS comment blocks
Originally posted by @hmajoros in #42 (comment)
The text was updated successfully, but these errors were encountered: