From 72770afab057c32a0fe8e098e8e2ff9a93b2f774 Mon Sep 17 00:00:00 2001 From: wagenet Date: Wed, 23 Nov 2022 17:09:46 +0000 Subject: [PATCH 001/103] Advance RFC to Stage recommended --- text/0659-unique-id-helper.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/text/0659-unique-id-helper.md b/text/0659-unique-id-helper.md index 9c4db39d6b..2a30452adb 100644 --- a/text/0659-unique-id-helper.md +++ b/text/0659-unique-id-helper.md @@ -1,14 +1,13 @@ --- -stage: released # FIXME: This may be recommended +stage: recommended start-date: 2020-08-25T00:00:00.000Z release-date: 2022-05-02T00:00:00.000Z release-versions: ember-source: v4.4.0 - teams: - framework prs: - accepted: https://github.com/emberjs/rfcs/pull/659 + accepted: 'https://github.com/emberjs/rfcs/pull/659' project-link: --- From 38547cd19a10c28ae5c8f2773ed85a9d8637b141 Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Wed, 23 Nov 2022 17:09:51 +0000 Subject: [PATCH 002/103] Update RFC 0659 recommended PR URL --- text/0659-unique-id-helper.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0659-unique-id-helper.md b/text/0659-unique-id-helper.md index 2a30452adb..ca333ec20f 100644 --- a/text/0659-unique-id-helper.md +++ b/text/0659-unique-id-helper.md @@ -8,6 +8,7 @@ teams: - framework prs: accepted: 'https://github.com/emberjs/rfcs/pull/659' + recommended: 'https://github.com/emberjs/rfcs/pull/865' project-link: --- From 7281eca4a6d519e3f619e491939f8879a5468a99 Mon Sep 17 00:00:00 2001 From: wagenet Date: Mon, 13 Mar 2023 19:55:07 +0000 Subject: [PATCH 003/103] Advance RFC {{ inputs.rfc-number }} to Stage recommended --- text/0776-typescript-blueprints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0776-typescript-blueprints.md b/text/0776-typescript-blueprints.md index 1daef59b51..26e393b6db 100644 --- a/text/0776-typescript-blueprints.md +++ b/text/0776-typescript-blueprints.md @@ -1,5 +1,5 @@ --- -stage: released +stage: recommended start-date: 2021-11-11T00:00:00.000Z release-date: 2022-12-08T00:00:00.000Z release-versions: From c0370fcf54ae6175be1f9279cee25606aa5baf77 Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Mon, 13 Mar 2023 19:55:11 +0000 Subject: [PATCH 004/103] Update RFC 0776 recommended PR URL --- text/0776-typescript-blueprints.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0776-typescript-blueprints.md b/text/0776-typescript-blueprints.md index 26e393b6db..60ac50b269 100644 --- a/text/0776-typescript-blueprints.md +++ b/text/0776-typescript-blueprints.md @@ -12,6 +12,7 @@ prs: accepted: 'https://github.com/emberjs/rfcs/pull/776' ready-for-release: 'https://github.com/emberjs/rfcs/pull/873' released: 'https://github.com/emberjs/rfcs/pull/911' + recommended: 'https://github.com/emberjs/rfcs/pull/912' project-link: --- From b9c80ce199a7a4e5170193bbbe87773b00471181 Mon Sep 17 00:00:00 2001 From: wagenet Date: Sat, 10 Jun 2023 15:07:22 +0000 Subject: [PATCH 005/103] Advance RFC {{ inputs.rfc-number }} to Stage recommended --- text/0811-element-modifiers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0811-element-modifiers.md b/text/0811-element-modifiers.md index 045eed0d5b..2611e069d9 100644 --- a/text/0811-element-modifiers.md +++ b/text/0811-element-modifiers.md @@ -1,5 +1,5 @@ --- -stage: released +stage: recommended start-date: 2022-03-29T00:00:00.000Z release-date: 2023-03-03T00:00:00.000Z release-versions: From f477635d20c887254b7923704543ad6eb6daa38f Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Sat, 10 Jun 2023 15:07:26 +0000 Subject: [PATCH 006/103] Update RFC 0811 recommended PR URL --- text/0811-element-modifiers.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0811-element-modifiers.md b/text/0811-element-modifiers.md index 2611e069d9..3feac9cf67 100644 --- a/text/0811-element-modifiers.md +++ b/text/0811-element-modifiers.md @@ -11,6 +11,7 @@ prs: accepted: 'https://github.com/emberjs/rfcs/pull/811' ready-for-release: 'https://github.com/emberjs/rfcs/pull/885' released: 'https://github.com/emberjs/rfcs/pull/928' + recommended: 'https://github.com/emberjs/rfcs/pull/934' project-link: --- From 211c4976413c7d637e271e6becce4196ae8050fe Mon Sep 17 00:00:00 2001 From: wagenet Date: Fri, 22 Sep 2023 19:16:10 +0000 Subject: [PATCH 007/103] Advance RFC 0774 to Stage recommended --- text/0774-implicit-record-route-loading.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0774-implicit-record-route-loading.md b/text/0774-implicit-record-route-loading.md index 467ac2d7b3..0cfec69696 100644 --- a/text/0774-implicit-record-route-loading.md +++ b/text/0774-implicit-record-route-loading.md @@ -1,5 +1,5 @@ --- -stage: released +stage: recommended start-date: 2021-11-14T00:00:00.000Z release-date: release-versions: From a53dd0302f616cc6dc97e5ad8d9037e2671e3355 Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Fri, 22 Sep 2023 19:16:14 +0000 Subject: [PATCH 008/103] Update RFC 0774 recommended PR URL --- text/0774-implicit-record-route-loading.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0774-implicit-record-route-loading.md b/text/0774-implicit-record-route-loading.md index 0cfec69696..71ff12d756 100644 --- a/text/0774-implicit-record-route-loading.md +++ b/text/0774-implicit-record-route-loading.md @@ -9,6 +9,7 @@ prs: accepted: 'https://github.com/emberjs/rfcs/pull/774' ready-for-release: 'https://github.com/emberjs/rfcs/pull/900' released: 'https://github.com/emberjs/rfcs/pull/955' + recommended: 'https://github.com/emberjs/rfcs/pull/970' --- # Deprecate Implicit Record Loading in Routes From 19fa0d945fd5819fa193fccddaa5ea1e82cc33cd Mon Sep 17 00:00:00 2001 From: Peter Wagenet Date: Fri, 22 Sep 2023 12:18:00 -0700 Subject: [PATCH 009/103] Fix release version --- text/0774-implicit-record-route-loading.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/text/0774-implicit-record-route-loading.md b/text/0774-implicit-record-route-loading.md index 71ff12d756..564f97dca0 100644 --- a/text/0774-implicit-record-route-loading.md +++ b/text/0774-implicit-record-route-loading.md @@ -1,8 +1,9 @@ --- stage: recommended start-date: 2021-11-14T00:00:00.000Z -release-date: +release-date: 2023-09-11T00:00:00.00Z release-versions: + ember-source: v5.3.0 teams: - framework prs: From 166023a2859c427a7f74ba2e0f7457c8b1486439 Mon Sep 17 00:00:00 2001 From: ef4 Date: Fri, 13 Oct 2023 18:05:36 +0000 Subject: [PATCH 010/103] Advance RFC 0918 to Stage released --- text/0918-deprecate-travis-ci-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0918-deprecate-travis-ci-support.md b/text/0918-deprecate-travis-ci-support.md index 4770a27fad..888f276ce3 100644 --- a/text/0918-deprecate-travis-ci-support.md +++ b/text/0918-deprecate-travis-ci-support.md @@ -1,5 +1,5 @@ --- -stage: ready-for-release +stage: released start-date: 2023-03-25T00:00:00.000Z release-date: release-versions: From 6c6d6328411e3d5b1414651f029ed5f79527fda1 Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Fri, 13 Oct 2023 18:05:40 +0000 Subject: [PATCH 011/103] Update RFC 0918 released PR URL --- text/0918-deprecate-travis-ci-support.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0918-deprecate-travis-ci-support.md b/text/0918-deprecate-travis-ci-support.md index 888f276ce3..9cf0ab20b3 100644 --- a/text/0918-deprecate-travis-ci-support.md +++ b/text/0918-deprecate-travis-ci-support.md @@ -9,6 +9,7 @@ teams: prs: accepted: 'https://github.com/emberjs/rfcs/pull/918' ready-for-release: 'https://github.com/emberjs/rfcs/pull/954' + released: 'https://github.com/emberjs/rfcs/pull/978' project-link: --- From 5cce5b2d6080493cf84b704e18db4292d5fda4ce Mon Sep 17 00:00:00 2001 From: Katie Gengler Date: Fri, 20 Oct 2023 13:29:26 -0400 Subject: [PATCH 012/103] Update Release versions and date --- text/0918-deprecate-travis-ci-support.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/text/0918-deprecate-travis-ci-support.md b/text/0918-deprecate-travis-ci-support.md index 9cf0ab20b3..168c55cda7 100644 --- a/text/0918-deprecate-travis-ci-support.md +++ b/text/0918-deprecate-travis-ci-support.md @@ -1,8 +1,9 @@ --- stage: released start-date: 2023-03-25T00:00:00.000Z -release-date: +release-date: 2023-12-11T00:00:00.000Z release-versions: + ember-cli: 5.5.0 teams: - cli - learning From 1401660094edf4b1a382bf0e3879ed0fcee47ea9 Mon Sep 17 00:00:00 2001 From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com> Date: Thu, 2 Nov 2023 15:38:57 -0400 Subject: [PATCH 013/103] initial --- text/0000-drop-safari-less-than-14.md | 92 +++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 text/0000-drop-safari-less-than-14.md diff --git a/text/0000-drop-safari-less-than-14.md b/text/0000-drop-safari-less-than-14.md new file mode 100644 index 0000000000..b7844691b0 --- /dev/null +++ b/text/0000-drop-safari-less-than-14.md @@ -0,0 +1,92 @@ +--- +stage: accepted +start-date: # In format YYYY-MM-DDT00:00:00.000Z +release-date: # In format YYYY-MM-DDT00:00:00.000Z +release-versions: +teams: # delete teams that aren't relevant + - cli + - data + - framework + - learning + - steering + - typescript +prs: + accepted: # Fill this in with the URL for the Proposal RFC PR +project-link: +suite: +--- + + + + +# Drop support for Safari < v14.1 + +## Summary + +Until v14.1, Safari doesn't support: +- private class fields: https://caniuse.com/mdn-javascript_classes_private_class_fields + +Other features in the ecosystem, + +class static initialization blocks: +- Safari 16.4: https://caniuse.com/mdn-javascript_classes_static_initialization_blocks + +This RFC is not concernd with static initialization blocks, as those can easily by transpiled without adding a a lot of code. + +## Motivation + +Private class field transpilation has a big impact on the kind of code emitted. We want to transpile as little as possible -- ideally nothing, and let app users decide if they need to transpile further. + +## Detailed design + +> This is the bulk of the RFC. + +> Explain the design in enough detail for somebody +familiar with the framework to understand, and for somebody familiar with the +implementation to implement. This should get into specifics and corner-cases, +and include examples of how the feature is used. Any new terminology should be +defined here. + +## How we teach this + +> What names and terminology work best for these concepts and why? How is this +idea best presented? As a continuation of existing Ember patterns, or as a +wholly new one? + +> Would the acceptance of this proposal mean the Ember guides must be +re-organized or altered? Does it change how Ember is taught to new users +at any level? + +> How should this feature be introduced and taught to existing Ember +users? + +## Drawbacks + +> Why should we *not* do this? Please consider the impact on teaching Ember, +on the integration of this feature with other existing and planned features, +on the impact of the API churn on existing apps, etc. + +> There are tradeoffs to choosing any path, please attempt to identify them here. + +## Alternatives + +> What other designs have been considered? What is the impact of not doing this? + +> This section could also include prior art, that is, how other frameworks in the same domain have solved this problem. + +## Unresolved questions + +> Optional, but suggested for first drafts. What parts of the design are still +TBD? From d51d2d461332bdf8adbba932a44a15c7adc6d0ef Mon Sep 17 00:00:00 2001 From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com> Date: Thu, 2 Nov 2023 15:40:40 -0400 Subject: [PATCH 014/103] Update frontmatter --- ...afari-less-than-14.md => 0984-drop-safari-less-than-14.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename text/{0000-drop-safari-less-than-14.md => 0984-drop-safari-less-than-14.md} (95%) diff --git a/text/0000-drop-safari-less-than-14.md b/text/0984-drop-safari-less-than-14.md similarity index 95% rename from text/0000-drop-safari-less-than-14.md rename to text/0984-drop-safari-less-than-14.md index b7844691b0..2aa48e9a8c 100644 --- a/text/0000-drop-safari-less-than-14.md +++ b/text/0984-drop-safari-less-than-14.md @@ -1,6 +1,6 @@ --- stage: accepted -start-date: # In format YYYY-MM-DDT00:00:00.000Z +start-date: 2023-11-02T15:40:00.000Z release-date: # In format YYYY-MM-DDT00:00:00.000Z release-versions: teams: # delete teams that aren't relevant @@ -11,7 +11,7 @@ teams: # delete teams that aren't relevant - steering - typescript prs: - accepted: # Fill this in with the URL for the Proposal RFC PR + accepted: https://github.com/emberjs/rfcs/pull/984 project-link: suite: --- From cbfe861e42a63978398afc2fa041b2cbe3ffa712 Mon Sep 17 00:00:00 2001 From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com> Date: Thu, 2 Nov 2023 16:38:00 -0400 Subject: [PATCH 015/103] specify --- text/0984-drop-safari-less-than-14.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/text/0984-drop-safari-less-than-14.md b/text/0984-drop-safari-less-than-14.md index 2aa48e9a8c..ebd1132a73 100644 --- a/text/0984-drop-safari-less-than-14.md +++ b/text/0984-drop-safari-less-than-14.md @@ -51,6 +51,9 @@ Private class field transpilation has a big impact on the kind of code emitted. ## Detailed design +Ember v6 Will not support Safari < v14.1 + + > This is the bulk of the RFC. > Explain the design in enough detail for somebody From 76611b6cba6048748331ac0c43aa48d78cfe244f Mon Sep 17 00:00:00 2001 From: Aaron Chambers Date: Fri, 3 Nov 2023 14:42:11 +0000 Subject: [PATCH 016/103] Apply suggestions from code review Co-authored-by: MrChocolatine <47531779+MrChocolatine@users.noreply.github.com> --- text/0984-drop-safari-less-than-14.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/text/0984-drop-safari-less-than-14.md b/text/0984-drop-safari-less-than-14.md index ebd1132a73..82fbdaa451 100644 --- a/text/0984-drop-safari-less-than-14.md +++ b/text/0984-drop-safari-less-than-14.md @@ -43,15 +43,15 @@ Other features in the ecosystem, class static initialization blocks: - Safari 16.4: https://caniuse.com/mdn-javascript_classes_static_initialization_blocks -This RFC is not concernd with static initialization blocks, as those can easily by transpiled without adding a a lot of code. +This RFC is not concerned with static initialization blocks, as those can easily be transpiled without adding a a lot of code. ## Motivation -Private class field transpilation has a big impact on the kind of code emitted. We want to transpile as little as possible -- ideally nothing, and let app users decide if they need to transpile further. +Private class fields transpilation has a big impact on the kind of code emitted. We want to transpile as little as possible -- ideally nothing, and let app users decide if they need to transpile further. ## Detailed design -Ember v6 Will not support Safari < v14.1 +Ember v6 will not support Safari < v14.1 > This is the bulk of the RFC. From 95020b0e7358457890479108d2b6cf8ec3819a9f Mon Sep 17 00:00:00 2001 From: ef4 Date: Fri, 1 Dec 2023 19:29:53 +0000 Subject: [PATCH 017/103] Advance RFC 0726 to Stage ready-for-release --- text/0726-dom-element-descriptor-interface.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/text/0726-dom-element-descriptor-interface.md b/text/0726-dom-element-descriptor-interface.md index 805dfbe7af..df41eb8aa7 100644 --- a/text/0726-dom-element-descriptor-interface.md +++ b/text/0726-dom-element-descriptor-interface.md @@ -1,17 +1,17 @@ --- -stage: accepted +stage: ready-for-release start-date: 2021-03-13T00:42:02.085Z -release-date: # In format YYYY-MM-DDT00:00:00.000Z +release-date: release-versions: -teams: # delete teams that aren't relevant +teams: - cli - framework - learning - typescript prs: - accepted: https://github.com/emberjs/rfcs/pull/726 + accepted: 'https://github.com/emberjs/rfcs/pull/726' project-link: -suite: +suite: --- # DOM Element descriptor interface for test helpers From 4a2e47927d932a33f067e63a222277b8bbb546bb Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Fri, 1 Dec 2023 19:29:57 +0000 Subject: [PATCH 018/103] Update RFC 0726 ready-for-release PR URL --- text/0726-dom-element-descriptor-interface.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0726-dom-element-descriptor-interface.md b/text/0726-dom-element-descriptor-interface.md index df41eb8aa7..b0b467515f 100644 --- a/text/0726-dom-element-descriptor-interface.md +++ b/text/0726-dom-element-descriptor-interface.md @@ -10,6 +10,7 @@ teams: - typescript prs: accepted: 'https://github.com/emberjs/rfcs/pull/726' + ready-for-release: 'https://github.com/emberjs/rfcs/pull/992' project-link: suite: --- From cbe53de65265bcf02f2ee5e56b7a81be359eedcb Mon Sep 17 00:00:00 2001 From: ef4 Date: Fri, 15 Dec 2023 19:21:12 +0000 Subject: [PATCH 019/103] Advance RFC 0918 to Stage recommended --- text/0918-deprecate-travis-ci-support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0918-deprecate-travis-ci-support.md b/text/0918-deprecate-travis-ci-support.md index 168c55cda7..fdfb43d610 100644 --- a/text/0918-deprecate-travis-ci-support.md +++ b/text/0918-deprecate-travis-ci-support.md @@ -1,5 +1,5 @@ --- -stage: released +stage: recommended start-date: 2023-03-25T00:00:00.000Z release-date: 2023-12-11T00:00:00.000Z release-versions: From c66656224982100533070db95470f3952df06089 Mon Sep 17 00:00:00 2001 From: "Ember.js RFCS CI" Date: Fri, 15 Dec 2023 19:21:15 +0000 Subject: [PATCH 020/103] Update RFC 0918 recommended PR URL --- text/0918-deprecate-travis-ci-support.md | 1 + 1 file changed, 1 insertion(+) diff --git a/text/0918-deprecate-travis-ci-support.md b/text/0918-deprecate-travis-ci-support.md index fdfb43d610..0e1b69f241 100644 --- a/text/0918-deprecate-travis-ci-support.md +++ b/text/0918-deprecate-travis-ci-support.md @@ -11,6 +11,7 @@ prs: accepted: 'https://github.com/emberjs/rfcs/pull/918' ready-for-release: 'https://github.com/emberjs/rfcs/pull/954' released: 'https://github.com/emberjs/rfcs/pull/978' + recommended: 'https://github.com/emberjs/rfcs/pull/994' project-link: --- From aace14e077fcb01baab22a73667d3b8044e7ff38 Mon Sep 17 00:00:00 2001 From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com> Date: Fri, 15 Dec 2023 14:38:31 -0500 Subject: [PATCH 021/103] Create 0000-deprecate-non-colocated-components.md --- ...0000-deprecate-non-colocated-components.md | 77 +++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 text/0000-deprecate-non-colocated-components.md diff --git a/text/0000-deprecate-non-colocated-components.md b/text/0000-deprecate-non-colocated-components.md new file mode 100644 index 0000000000..cefef1b3aa --- /dev/null +++ b/text/0000-deprecate-non-colocated-components.md @@ -0,0 +1,77 @@ +--- +stage: accepted +start-date: +release-date: +release-versions: +teams: # delete teams that aren't relevant + - cli + - data + - framework + - learning + - steering + - typescript +prs: + accepted: # update this to the PR that you propose your RFC in +project-link: +--- + + + +# Deprecate non-co-located components. + +## Summary + +Deprecates +- classic component layout +- pods component layout + +## Motivation + +> Why are we doing this? What are the problems with the deprecated feature? +What is the replacement functionality? + +## Transition Path + +> This is the bulk of the RFC. Explain the use-cases that deprecated functionality +covers, and for each use-case, describe the transition path. +Describe it in enough detail for someone who uses the deprecated functionality +to understand, for someone to write the deprecation guide, and for someone +familiar with the implementation to implement. + +## How We Teach This + +> Would the acceptance of this proposal mean the Ember guides must be +re-organized or altered? Does it change how Ember is taught to new users +at any level? +Does it mean we need to put effort into highlighting the replacement +functionality more? What should we do about documentation, in the guides +related to this feature? +How should this deprecation be introduced and explained to existing Ember +users? + +## Drawbacks + +> Why should we *not* do this? Please consider the impact on teaching Ember, +on the integration of this feature with other existing and planned features, +on the impact of the API churn on existing apps, etc. +There are tradeoffs to choosing any path, please attempt to identify them here. + +## Alternatives + +> What other designs have been considered? What is the impact of not doing this? + +## Unresolved questions + +> Optional, but suggested for first drafts. What parts of the design are still +TBD? From f1757801330b86da7854072b411707f6b1a88d6d Mon Sep 17 00:00:00 2001 From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com> Date: Fri, 15 Dec 2023 15:16:24 -0500 Subject: [PATCH 022/103] Actually write the thing --- ...0000-deprecate-non-colocated-components.md | 77 ---------- ...0995-deprecate-non-colocated-components.md | 132 ++++++++++++++++++ 2 files changed, 132 insertions(+), 77 deletions(-) delete mode 100644 text/0000-deprecate-non-colocated-components.md create mode 100644 text/0995-deprecate-non-colocated-components.md diff --git a/text/0000-deprecate-non-colocated-components.md b/text/0000-deprecate-non-colocated-components.md deleted file mode 100644 index cefef1b3aa..0000000000 --- a/text/0000-deprecate-non-colocated-components.md +++ /dev/null @@ -1,77 +0,0 @@ ---- -stage: accepted -start-date: -release-date: -release-versions: -teams: # delete teams that aren't relevant - - cli - - data - - framework - - learning - - steering - - typescript -prs: - accepted: # update this to the PR that you propose your RFC in -project-link: ---- - - - -# Deprecate non-co-located components. - -## Summary - -Deprecates -- classic component layout -- pods component layout - -## Motivation - -> Why are we doing this? What are the problems with the deprecated feature? -What is the replacement functionality? - -## Transition Path - -> This is the bulk of the RFC. Explain the use-cases that deprecated functionality -covers, and for each use-case, describe the transition path. -Describe it in enough detail for someone who uses the deprecated functionality -to understand, for someone to write the deprecation guide, and for someone -familiar with the implementation to implement. - -## How We Teach This - -> Would the acceptance of this proposal mean the Ember guides must be -re-organized or altered? Does it change how Ember is taught to new users -at any level? -Does it mean we need to put effort into highlighting the replacement -functionality more? What should we do about documentation, in the guides -related to this feature? -How should this deprecation be introduced and explained to existing Ember -users? - -## Drawbacks - -> Why should we *not* do this? Please consider the impact on teaching Ember, -on the integration of this feature with other existing and planned features, -on the impact of the API churn on existing apps, etc. -There are tradeoffs to choosing any path, please attempt to identify them here. - -## Alternatives - -> What other designs have been considered? What is the impact of not doing this? - -## Unresolved questions - -> Optional, but suggested for first drafts. What parts of the design are still -TBD? diff --git a/text/0995-deprecate-non-colocated-components.md b/text/0995-deprecate-non-colocated-components.md new file mode 100644 index 0000000000..142d0f71e2 --- /dev/null +++ b/text/0995-deprecate-non-colocated-components.md @@ -0,0 +1,132 @@ +--- +stage: accepted +start-date: 2023-12-15 +release-date: +release-versions: +teams: # delete teams that aren't relevant + - cli + - framework + - learning + - typescript +prs: + accepted: https://github.com/emberjs/rfcs/pull/995 +project-link: +--- + + + +# Deprecate non-co-located components. + +## Summary + +Deprecates +- classic component layout +- pods component layout + + +After "ember@6", only the following will be allowed: +- co-located components +- gjs / gts components + +## Motivation + +These older component layouts force build tooling to keep a lot of resolution rules around, and makes it hard for codemods and other community tooling to effectively work across folks' projects. + + +## Transition Path + +There are two types of paths to migrate off the old layouts +- use a currently supported multi-file layout (keeping separate `js`, `ts`, and hbs files) +- migrate the component entirely to the latest component format, `gjs`, `gts`, (aka `