Closed LoiKos closed 5 years ago
Okay, I was able to reproduce this.
~It appears like this is not a bug, and instead a feature.~ It's both
I'm not using flow but as I looked into docs, the culprit is your type
variable, which is being treated as flow type annotation.
Now there are two things —
flow_types
option in your JSCustom User Settings and remove that (Only if you are not using flow)type
as a variable name.I hope this helps.
Oh okay i find that flow_types
option i'll take a look... I don't yet if i remove this or if i change my variable name but it helps thanks !
When the flow syntax extension sees type
at the beginning of the line, it assumes that it's a type annotation. This should be an easy fix. If I don't get to it today due to the holidays, it should be fixed by Wednesday.
By the way, in the immediate term you can work around this by wrapping the statement in parens:
(type = 'Ex/ample');
v1.0.28 should fix this. Please let me know if it does not.
it's fix with v1.0.28 :+1:
i have a bug using a / in a string that break the syntax coloration :