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 }}
*/
I'm not 100% sure ^^^ is what is happening.
I'm getting this report on my prettier plugin:
The plugin just passes the file contents to
preprocessEmbeddedTemplates
though:https://github.com/gitKrystan/prettier-plugin-ember-template-tag/blob/1ab2de020a80cb507d69007aeaf6901b3f654221/src/parse.ts#L56-L66
The text was updated successfully, but these errors were encountered: