Currently, in both Glint 1 and Volar-ized Glint 2, the presence of any kind of syntax error within a <template> tag (in a gts file) breaks all auto-complete/auto-import functionality. Basically it's very difficult to start typing in a component name within a <template> tag and see any auto-complete/auto-import suggestions unless you awkwardly make the syntax valid for long enough to finish an auto-complete. Examples:
invalid syntax due to unclosed <: no autocomplete:
no < at all, ... less obvious case, but guessing we'd still want an auto-complete suggestion?
auto complete suggestions kick in, but only after awkwardly typing in correct syntax and going back to open element
How to implement
There may be somewhat hacky ways to get this working without changing our gts/glimmer parser to be more forgiving; need to check in the Volar discord. But perhaps we do need/want a forgiving Glimmer parser. Haven't looked into that too deeply though.
Currently, in both Glint 1 and Volar-ized Glint 2, the presence of any kind of syntax error within a
<template>tag (in a gts file) breaks all auto-complete/auto-import functionality. Basically it's very difficult to start typing in a component name within a<template>tag and see any auto-complete/auto-import suggestions unless you awkwardly make the syntax valid for long enough to finish an auto-complete. Examples:invalid syntax due to unclosed
<: no autocomplete:no
<at all, ... less obvious case, but guessing we'd still want an auto-complete suggestion?auto complete suggestions kick in, but only after awkwardly typing in correct syntax and going back to open element
How to implement
There may be somewhat hacky ways to get this working without changing our gts/glimmer parser to be more forgiving; need to check in the Volar discord. But perhaps we do need/want a forgiving Glimmer parser. Haven't looked into that too deeply though.