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
We have Closure templates which begin with a SoyDoc comment before {namespace}. The closure compiler doesn't seem to mind so I'm guessing it just treats it as a regular comment. But the plugin treats it as an error, and doesn't parse/syntax highlight the rest of the file. The error produced is:
mismatched input '/**' expecting '{namespace'
Here's an example template file which triggers it:
/** * SoyDoc at beginning of file and before {namespace} */{namespacetesting}
Another example:
/***********/{namespacetesting}
The plugin shouldn't report it as an error if the closure compiler accepts it.
The text was updated successfully, but these errors were encountered:
We have Closure templates which begin with a SoyDoc comment before
{namespace}
. The closure compiler doesn't seem to mind so I'm guessing it just treats it as a regular comment. But the plugin treats it as an error, and doesn't parse/syntax highlight the rest of the file. The error produced is:Here's an example template file which triggers it:
Another example:
The plugin shouldn't report it as an error if the closure compiler accepts it.
The text was updated successfully, but these errors were encountered: