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
Our fundamental restriction right now is that @glimmer/syntax doesn't have an error-tolerant parsing option and will only provide an AST for a 100% valid template. Because of that, we can autocomplete for @args and named blocks, but only if you go out of your way to ensure your surrounding template is syntactically valid.
For named blocks especially, that's pretty much useless, as the only way to get completions is to make it self-closing, go back and trigger a suggestion, then un-self-close the block and add the closing tag.
Both for Glint itself and for other tools like template-lint it would be super helpful for @glimmer/syntax to have an error-tolerant mode that gave a best-effort parse tree. With that, we could better support these and a bunch of other completion scenarios with little to no change on this end.
I know others are interested in that, and I'm banging the drum—yesterday in #st-typescript for instance 😄. For now there are still a ton of other things to do in Glint proper, but if we reach a point of readiness here that this completion pain makes it to the top of the priority list and no one else has been able to make progress with the parser in the meantime, I may take a look.
Right now it doesn't appear that we autocomplete for
@
arguments on components or named blocks.The text was updated successfully, but these errors were encountered: