Skip to content
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

[BUGFIX beta] Make sure the component-class blueprint generates a signature in a TS project #20645

Conversation

bertdeblock
Copy link
Member

Closes #20598.

` Element: null;`;

return (
`interface ${componentName}Signature {${EOL}` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally the guidance we've given with Glint is to always export your signature, since it's useful when you start talking about places where other components are yielding or or accepting this one as an arg.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dfreeman. Updated accordingly.

@bertdeblock bertdeblock force-pushed the fix-component-class-blueprint-in-ts-project branch from 632a6ce to a362683 Compare February 7, 2024 12:04
@kategengler kategengler merged commit 16357a2 into emberjs:main Feb 15, 2024
20 checks passed
@kategengler
Copy link
Member

Thank you!

@kategengler kategengler changed the title Make sure the component-class blueprint generates a signature in a TS project [BUGFIX beta] Make sure the component-class blueprint generates a signature in a TS project Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] ember g component-class foo does not generate a component signature in a TypeScript project
3 participants