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
The module name has a strange coloring, with everything till the first dot green, and the rest white.
Comments inside the declaration are not colored.
Environment
Operating System: Windows 10
JDK version: 14
Visual Studio Code version: 1.44.0
Java extension version: 0.59.1
Steps To Reproduce
create a module-info.java file with the following contents:
/** * ok */modulecom.foo.bar {
// not ok/* not ok */requiresjava.base;
}
// ok/* ok */
Current Result
Expected Result
The module name should be all white (since that's the coloring of module names inside the declaration).
Comments inside the declaration should be colored as such.
The text was updated successfully, but these errors were encountered:
Now that atom/language-java#246 is merged, one would think that this issue can be closed. Indeed, that fix made it into VS Code 1.54.0 via microsoft/vscode@b37252c. But the problem is that this extension embeds an older version of the same TextMate grammar (see #1638), which doesn't include the fix, but still overrides the new version included in VS Code. The end result being that comments in module declarations are still not highlighted (the remaining part of this issue).
One solution would be to simply update the included TextMate grammar included in this extension. Another solution would be to stop embedding the grammar and let VS Code provide it instead (since it now has the more recent version).
The module name has a strange coloring, with everything till the first dot green, and the rest white.
Comments inside the declaration are not colored.
Environment
Steps To Reproduce
Current Result
Expected Result
The module name should be all white (since that's the coloring of module names inside the declaration).
Comments inside the declaration should be colored as such.
The text was updated successfully, but these errors were encountered: