Document / Fix Language and File Naming Constraints

[CharlieIGG]

Document / Fix Language and File Naming Constraints

[marcoroth]

Hey @CharlieIGG, thanks for opening this issue!

You are right, the extension is probably too optimistic as-is right now. But both of the constraints you outlined are goals that I want to cover with the LSP.

1. is tracked in marcoroth/stimulus-parser#9
2. is tracked in marcoroth/stimulus-parser#29

The TypeScript one turned out harder than expected. I have a WIP version using the actual typescript parser using the Compiler API, but it's not really nice to work with. So I'm a little stuck on that one.

Please let me know if you have any insights or want to help. Thank you!

[CharlieIGG]

Hey @marcoroth I'll try to have a stab at it in the next few days.

[marcoroth]

Awesome @CharlieIGG, let me know if I can assist you in any way or have questions

[CharlieIGG]

You can review this :) marcoroth/stimulus-parser#47

EDIT – Never mind, this is failing during build... need to figure out a fix

[CharlieIGG]

Things are not looking great with acorn-typescript.

TSQuery looks more promising, but having no experience with it, it's taking me a while to figure out. I have a separate PR (WIP) here: marcoroth/stimulus-parser#48

I'll let you know as soon as I have something worth reviewing @marcoroth

[marcoroth]

Hey @CharlieIGG, thanks for giving this a shot. Yeah, I think acorn-typescript looks more promising than it actually is. Also because it's not really feature-complete.

I'm actually surprised that there isn't a nice and easy-to-use TypeScript parser available.

Granted, I didn't know about TSQuery, but this already looks more promising!