We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I believe this'd be fixed by using content-tag
content-tag
ember-template-imports
pre
<pre>
@glint/environment-ember-template-imports
transform
parse
Evidence:
[lint:types] app/templates/application.gjs:38:3 - error TS2657: JSX expressions must have one parent element. [lint:types] [lint:types] 38 <template> [lint:types] ~~~~~~~~~~ [lint:types] 39 {{pageTitle "is Polaris ready yet?"}} [lint:types] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [lint:types] ... [lint:types] 97 [lint:types] [lint:types] 98 <Footer /> [lint:types] ~~~~~~~~~~~~~~ [lint:types] [lint:types] app/templates/application.gjs:39:17 - error TS1005: ',' expected. [lint:types] [lint:types] 39 {{pageTitle "is Polaris ready yet?"}}
From: https://github.com/NullVoxPopuli/is-polaris-ready-yet/blob/40e70a330dcd94110910aa4dc1b29a757e90ec90/package.json#L31
The text was updated successfully, but these errors were encountered:
See typed-ember/glint#694
c50db17
5bdb53e
Successfully merging a pull request may close this issue.
I believe this'd be fixed by using
content-tag
content-tag
instead ofember-template-imports
#655pre
, when<pre>
is mentioned in test name of gts test file #617content-tag
in@glint/environment-ember-template-imports
#609transform
callback function: For linting, we'd need to be able to emit a full AST, including nodes for the template embroider-build/content-tag#39 (comment)content-tag
provide char-indexes for theparse
result in addition to the existing byte-indexesEvidence:
From: https://github.com/NullVoxPopuli/is-polaris-ready-yet/blob/40e70a330dcd94110910aa4dc1b29a757e90ec90/package.json#L31
The text was updated successfully, but these errors were encountered: