Jason Rogers

This seems to be a related case. Prettier changes this (dummy example): ``` const newObj = { ...(includeOptions ? options : {}) }; ``` to this: ``` const newObj =...

@vjeux I just tried to reproduce this in the playground and can't seem to do so. An analogous (but somewhat more complicated) situation just happened in a codebase I'm working...

@vjeux Ah, it seems to happen only when using the TypeScript parser specifically. Is it still appropriate to open a separate issue here in that case?

I wouldn't mind taking a shot at this feature. if it's still up for grabs. It'd be useful.

For the "find usages" and "find definitions" features, what are you envisioning?

@bd82 Sorry, I unfortunately haven't had a whole lot of time to work on this lately. I _did_ finally get to do an initial pass through today, though; you can...

> * We can go for MVP as the first step. Cool. That seems to me to be the right way to go, too. > * I am not sure...

> Won't it create ambiguius EBNF? Yes, you're right. That's enough to convince me. I also realized that there are other problematic cases, such as when the RegExp pattern is...

Another question: what do we do with tokens that have [custom token patterns](https://sap.github.io/chevrotain/docs/guide/custom_token_patterns.html)?

Hi, everyone. I got pointed to this thread by a [comment](https://community.stardog.com/t/language-server-protocol/1426/3) over on the Stardog community forum. At Stardog, we've been using the Language Server Protocol to integrate language intelligence...