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

Enable EMBER_TYPESCRIPT_BLUEPRINTS flag #20352

Conversation

bertdeblock
Copy link
Member

Closes #20177.

Copy link
Contributor

@chriskrycho chriskrycho left a comment

Choose a reason for hiding this comment

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

Seems good here – let me know when you're ready to move it out of Draft!

@bertdeblock bertdeblock marked this pull request as ready for review January 19, 2023 07:25
@bertdeblock
Copy link
Member Author

@chriskrycho Done! Was mostly waiting on a "good to go", wasn't sure if we could already land this.

@chriskrycho
Copy link
Contributor

Yeah, let me do a quick pass on the actual blueprints to make sure they're good, but/and we should have folks kick the tires a bunch during the 4.12 beta cycle—that’s what the beta cycle is for!

@chriskrycho
Copy link
Contributor

We need to add the service registry to the service blueprints, but I believe we're otherwise good to go; I'm putting up a PR to do that now.

@chriskrycho
Copy link
Contributor

chriskrycho commented Jan 19, 2023

Chatting with @cafreeman, he reminded me that we also need the blueprints to support generating signatures for components! And the same will go for helper classes, and we should make sure ember-modifier’s blueprints are updated as well.

@chriskrycho
Copy link
Contributor

All right, let's do this! 🎉 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature TypeScript Work on Ember’s types
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable EMBER_TYPESCRIPT_BLUEPRINTS feature
2 participants