-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
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
Use content tag #615
Use content tag #615
Conversation
packages/environment-ember-template-imports/-private/environment/preprocess.ts
Show resolved
Hide resolved
69a0e76
to
e9d1d0c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- content-tag requires syntax to be correct
- LSPs need fault-tolerant parsing to aid in intellisense, suggestions and all that
This isn't a new problem for Glint, but it does take things in the wrong direction a bit.
Based on Ed's research yesterday, it sounds like this isn't quite true, which is great news!
packages/environment-ember-template-imports/-private/environment/preprocess.ts
Outdated
Show resolved
Hide resolved
import { Preprocessor } from 'content-tag'; | ||
const p = new Preprocessor(); | ||
|
||
interface Parsed { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have content-tag
expose this type itself, either by generating it from the underlying Rust struct(s) or something like #[wasm_bindgen(typescript_custom_section)]
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so -- tho I don't know how specific we'd get. @ef4 said an update to one of the build tools would give us better types when updated.
It's also totally reasonable for us to ship our own d.ts, and ignore the generated one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not too hung up on any specific approach on the content-tag
side; it just makes me nervous to be encoding assumptions here that could break at any time 😅
packages/environment-ember-template-imports/-private/environment/preprocess.ts
Outdated
Show resolved
Hide resolved
22c9b01
to
8f76ccc
Compare
251c574
to
f6ba22a
Compare
I broke something here, so I'm starting over here: #655 |
Resolves: #609
Blocked by: embroider-build/content-tag#19Blocked by: embroider-build/content-tag#31Unblocks: NullVoxPopuli/polaris-starter#11
Problem:
This isn't a new problem for Glint, but it does take things in the wrong direction a bit.