From fb7da84e9ef90b141df4d3d57674955b35a8f7a5 Mon Sep 17 00:00:00 2001 From: Chris Krycho Date: Fri, 12 Mar 2021 20:27:44 -0700 Subject: [PATCH 1/2] Clarify TypeScript RFC comments in Ember Times 175 --- content/the-ember-times-issue-175.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/the-ember-times-issue-175.md b/content/the-ember-times-issue-175.md index 9f8fe9c56..a7ec4ce3c 100644 --- a/content/the-ember-times-issue-175.md +++ b/content/the-ember-times-issue-175.md @@ -45,9 +45,9 @@ 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 * 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)! From c71cb832a72bbef0a80a80319c7bd5d4aaf2258a Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Fri, 12 Mar 2021 19:51:38 -0800 Subject: [PATCH 2/2] Make copy edit --- content/the-ember-times-issue-175.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/the-ember-times-issue-175.md b/content/the-ember-times-issue-175.md index a7ec4ce3c..504744520 100644 --- a/content/the-ember-times-issue-175.md +++ b/content/the-ember-times-issue-175.md @@ -44,7 +44,7 @@ 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. +* 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)