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
Currently T4Editor is leaning heavily on the use of RegEx patterns to filter out codeblocks from the textView and colorize them.
A better approach would be to create something that parses the textView on a token based implemenation. We only catch the T4 open/close tags and this leaves room to try and introduce C# language features inside these blocks.
The text was updated successfully, but these errors were encountered:
Can we at least replace the regex things with a custom parser for a better performance? And later think about "C# language features inside these blocks".
Currently it feels "laggy" with a large template on my i3 notebook. I suspect it is caused by the RegEx thing.
It seems not difficult to parse these tags. And as a bonus can try to add an error if tag is unclosed/unopened.
Currently T4Editor is leaning heavily on the use of RegEx patterns to filter out codeblocks from the textView and colorize them.
A better approach would be to create something that parses the textView on a token based implemenation. We only catch the T4 open/close tags and this leaves room to try and introduce C# language features inside these blocks.
The text was updated successfully, but these errors were encountered: