Closed vispariana closed 2 weeks ago
It´s not just with Linq, it happens with any anonymous type.
happening here as well
Any update on this?
Since this issue was opened we have added semantic highlighting support as well as a much improved textmate grammar.
Defining a new anonumous object having a field valued by LINQ breaks syntax highlighting.
Steps to reproduce: write the following code
Note: found out that if i put parentheses around the LINQ it is fixed, but i think it should be working without the parentheses either, because the code also works that way!