-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Tooling team meeting 2023-12-19.md #564
Conversation
|
||
### TypeScript team | ||
|
||
- rollup TypeScript team into the tooling team |
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 see what you did there 👀
- TODO: investigate -- does ember-intl use `moduleName`? we know the inspector does | ||
- ember language server's ember-intl integration? | ||
- Idea: `<template>` doesn't emit `moduleName` | ||
- need to communicate that `moduleName` is optional / sometimes missing |
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.
This is already the case – precompile
has moudleName
marked as optional, technically, moduleName
on the template is always present, but only because we default it to this string https://github.com/glimmerjs/glimmer-vm/blob/cb867e388d0de3547b3f4ebc10e2e92c95b75d7e/packages/%40glimmer/compiler/lib/compiler.ts#L128
So it would be non-breaking, at least technically speaking, to always set it to that string, and consumers should already be accounting for that
No description provided.