-
-
Notifications
You must be signed in to change notification settings - Fork 408
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
Author Built-In Blueprints in TypeScript #776
Conversation
Thanks for working on this @cafreeman! |
This seems like a great idea! I look forward to reviewing it in detail. |
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 100% on board with this and, at this point, don't have any concerns or further suggestions!
"How we teach this" should probably cover authoring blueprints, in as much as they are covered on the cli guides. See https://cli.emberjs.com/release/advanced-use/blueprints/ |
We discussed this in today's ember-cli team meeting, and are generally in favor of moving forward. There were a few things called out during that discussion that we think needs to be updated:
@cafreeman - Once those tweaks are made, I think this will be ready for another look. |
Thanks for the feedback @kategengler and @rwjblue! I've just pushed an update that should address both issues that were brought up. Let me know if you've got any other comments! |
Thanks for the updates @cafreeman!! We discussed this at the last ember-cli team meeting, and are moving this into final comment period. |
Advance RFC #776 "Author built-in blueprints in Typescript" to Stage Ready for Release
Advance RFC #776 `"Author Built-In Blueprints in TypeScript"` to Stage Released
Advance RFC #776 `"Author Built-In Blueprints in TypeScript"` to Stage Recommended
In order to support both TypeScript and JavaScript as official languages in Ember, we should enable blueprints to be written in TypeScript and (optionally) transformed to JavaScript. We should also convert all of the existing built-in blueprints to TypeScript to take advantage of this new functionality and lay the groundwork for future TypeScript inclusion efforts.
rendered