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.

Sign up for GitHub

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

Jump to bottom

Clarify TypeScript RFC comments in Ember Times 175 #933

Merged
merged 2 commits into from
Mar 13, 2021
Merged

Clarify TypeScript RFC comments in Ember Times 175 #933

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fb7da84
Clarify TypeScript RFC comments in Ember Times 175
chriskrycho Mar 13, 2021
c71cb83
Make copy edit
amyrlam Mar 13, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/the-ember-times-issue-175.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,10 @@ P.S. Please spread the word about the survey, ask your friends and coworkers to

> Ember officially supporting TypeScript means: All libraries which are installed as part of the default blueprint must ship accurate and up-to-date type definitions for the current edition. These types will uphold a Semantic Versioning commitment which includes a definition of SemVer for TypeScript types as well as a specification of supported compiler versions and settings, so that TypeScript will receive the same stability commitments as the rest of Ember.

* Any addon that is part of the default blueprint must ship types.
* The RFC explicitly does not require support for “typed templates”
* Instead of opting into TypeScript using [ember-cli-typescript](https://github.com/typed-ember/ember-cli-typescript) it should be done by default
* Any addon that is part of the default blueprint must ship types
* Define a policy on what constitutes a breaking change for consumers of a library which publishes types, including Ember’s core libraries
* New Ember apps and addons should support TypeScript by default, though the details of what tha means (for example how it will use [ember-cli-typescript](https://github.com/typed-ember/ember-cli-typescript) or not) will be resolved in future RFCs
* The RFC explicitly does not require support for “typed templates” (though the community is working on this and think it’s key to the long-term TypeScript story)

Read and comment on the [RFC on GitHub](https://github.com/emberjs/rfcs/pull/724)!

Expand Down