Alex Matchneer
Alex Matchneer
@mkszepp are you seeing type-checking functionality work properly in .gts files? e.g. if you introduce type error does it display an error, and/or if you hover a keyword does it...
@mkszepp Correct, you want built-in TS enabled; the default/built-in tsserver that VSCode spins up loads our TS Plugin and provides type-checking language tooling for .gts/.hbs all on its own. The...
Please create a separate issue for auto-complete; can keep this issue focused on syntax.
@davidtaylorhq I'm not opposed to this, but could you share what issues you're running into using the stable VSCode Plugin with the unstable Glint LS? I've been using this configuration...
FYI we've been pushing pre-release Glint VSCode extension for quite a while now and will continue to do so as we near v2 release (next week-ish).
Can you try out [Glint 2](https://github.com/typed-ember/glint/blob/main/GLINT_V2.md) and let me know if this is still an issue?
@deanylev can you try [Glint 2](https://github.com/typed-ember/glint/blob/main/GLINT_V2.md) to see if that fixes anything for you? It's possible that Glint 2's rearchitecting to work atop TS Plugin _might_ fix your OOM issues.
@cacique-coder I'm running into this as well for Ruby. All of the datatypes are defined as `:Object:` when many of them should be `:Array:`
@bertdeblock what runtime error do you encounter?
Sounds like our options are: 1. Babel transform or some other config/hack to get extension'd import module specifiers working correctly in classic build 2. Upstream Volar fix (if one is...