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}
*/
{namespace testing}
Another example:
/***********/
{namespace testing}
The plugin shouldn't report it as an error if the closure compiler accepts it.
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.