Shahar Soel

Yeah I have not implemented that feature or other newer RegExp features. Although I doubt it should be too complex as it is very similar to lookahead...

Hello @ConradIrwin Thanks for the PR. Are you using this library directly or via Chevrotain? The reason I am asking is that I am interested in **deprecating** this library and...

Thanks @ConradIrwin , Please let me know if you have any issues with `regexpp` the main reason I want to use it is to reduce TCO and need to maintain...

Thanks for reporting this @GordonSmith Do you know which version of ECMAScript added this syntax? This makes wonder again if I could transition Chevrotain to user another regExp parser (one...

> Out of curiosity why does Chevrotain need to parse the RegEx? I would have thought using them "black box" would have been sufficient? It is not mandatory, just for...

> as a potential side project I could see a "chevrotain grammar -> VSCode Language Extension" utility being able to get a huge % of the grunt work automated. I...

I have created some editor logic utils specifically for the XML language. The most complex case is the content assist logic which is responsible for understanding the content assist **syntactic...

Regarding the CST structure. it is intentionally very simple to allow fast construction and traversal. You may be able to override methods from the tree builder trait to change the...

Perhaps a prettier plugin is relevant for you, here are a couple of examples using Chevrotain: - https://github.com/jhipster/prettier-java/ - https://github.com/prettier/plugin-xml Although as you mentioned you main issue is the parsing...

Lexing modes would likely resolve these without needing "real" parser context.