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
As discussed here: #702 (comment), the correct syntax highlighting of JS files seems to go away as soon as the symbols got computed for a JS file.
Detailed steps how to reproduce this are here: #702 (comment)
It looks like the semantic highlighting of LSP4E seems to be involved here, but we need to investigate this. It works fine in Eclipse JEE 2023-03 builds as well as the latest WWD releases, so maybe related to the LSP4E snapshot version that we include in STS builds.
The text was updated successfully, but these errors were encountered:
Ok, I think this is indeed related to semantic highlighting done by LSP4E, so filed the issue over here: eclipse-lsp4e/lsp4e#537 - closing this one here as a duplicate now.
This is now fixed the latest lsp4e snapshot builds, so the next STS 4.18.0 CI build will pick that up automatically and the next release (scheduled for next week) should include this fix as well.
As discussed here: #702 (comment), the correct syntax highlighting of JS files seems to go away as soon as the symbols got computed for a JS file.
Detailed steps how to reproduce this are here: #702 (comment)
It looks like the semantic highlighting of LSP4E seems to be involved here, but we need to investigate this. It works fine in Eclipse JEE 2023-03 builds as well as the latest WWD releases, so maybe related to the LSP4E snapshot version that we include in STS builds.
The text was updated successfully, but these errors were encountered: