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
Is your feature request related to a problem? Please describe.
There was previously an issue with the Preview LSP option where the UI Guides wouldn't work. When that was fixed, I turned it back on and noticed the syntax highlighting was different. I opened #3155 and I was able to change the colour of the variables. However, the @ and override have different colours and it doesn't match. Prior to turning on Preview LSP, using the One Dark Pro theme the @override would be pink. I do not care about what colour it is so long as they have the same colour.
Describe the solution you'd like
As advised by @DanTup in the previous issue, I would like to have a token for annotations so the @ colour can be customised.
I've changed annotations to by default be coloured the same as variables:
This won't match perfectly if you use a constructor directly (@ClassFoo()) as classes are coloured slightly differently, but I think in most cases annotations are fields/getters.
You can also override the colour of the @ using the annotation token in your settings like:
Is your feature request related to a problem? Please describe.
There was previously an issue with the Preview LSP option where the UI Guides wouldn't work. When that was fixed, I turned it back on and noticed the syntax highlighting was different. I opened #3155 and I was able to change the colour of the variables. However, the
@
andoverride
have different colours and it doesn't match. Prior to turning on Preview LSP, using the One Dark Pro theme the@override
would be pink. I do not care about what colour it is so long as they have the same colour.Describe the solution you'd like
As advised by @DanTup in the previous issue, I would like to have a token for annotations so the
@
colour can be customised.Additional context
Issue #3155
The text was updated successfully, but these errors were encountered: