From 443654203e52e3d11611f72af1a34ac238dbc8dd Mon Sep 17 00:00:00 2001 From: Katie Gengler Date: Tue, 8 Apr 2025 11:56:54 -0400 Subject: [PATCH] Add RFCs to ember-data 5.x deprecations (for which I could find the RFCs) --- content/ember-data/v5/ember-data-deprecate-legacy-imports.md | 3 +++ content/ember-data/v5/ember-data-deprecate-non-strict-types.md | 3 +++ .../v5/ember-data-deprecate-store-extends-ember-object.md | 3 ++- 3 files changed, 8 insertions(+), 1 deletion(-) diff --git a/content/ember-data/v5/ember-data-deprecate-legacy-imports.md b/content/ember-data/v5/ember-data-deprecate-legacy-imports.md index e65d576b..1d5de3e1 100644 --- a/content/ember-data/v5/ember-data-deprecate-legacy-imports.md +++ b/content/ember-data/v5/ember-data-deprecate-legacy-imports.md @@ -3,6 +3,7 @@ title: Legacy Imports until: '6.0' since: '5.3' displayId: ember-data:deprecate-legacy-imports +rfc: https://rfcs.emberjs.com/id/0743-ember-data-deprecate-legacy-imports --- Deprecates importing from `ember-data/*` instead of `@ember-data/*` in order to prepare for the eventual removal of the legacy `ember-data/*` @@ -10,3 +11,5 @@ Deprecates importing from `ember-data/*` instead of `@ember-data/*` in order to All imports from `ember-data/*` should be updated to `@ember-data/*` except for `ember-data/store`. When you are using `ember-data` (as opposed to installing the individual packages) you should import from `ember-data/store` instead of `@ember-data/store` in order to receive the appropriate configuration of defaults. + +This deprecation was introduced in RFC [#0743](https://rfcs.emberjs.com/id/0743-ember-data-deprecate-legacy-imports). \ No newline at end of file diff --git a/content/ember-data/v5/ember-data-deprecate-non-strict-types.md b/content/ember-data/v5/ember-data-deprecate-non-strict-types.md index 92918253..a656878b 100644 --- a/content/ember-data/v5/ember-data-deprecate-non-strict-types.md +++ b/content/ember-data/v5/ember-data-deprecate-non-strict-types.md @@ -3,6 +3,7 @@ title: Non Strict Types until: '6.0' since: '5.3' displayId: ember-data:deprecate-non-strict-types +rfc: https://rfcs.emberjs.com/id/0740-ember-data-deprecate-non-strict-types --- Currently, EmberData expects that the `type` property associated with a resource follows several conventions. @@ -20,3 +21,5 @@ E.G. It will matter not that your string is in a specific format like singular, If using @ember-data/model, there will always be a restriction that the `type` must match the path on disk where the model is defined. e.g. `app/models/foo/bar-bem.js` must have a type of `foo/bar-bem` + +This deprecation was introduced in RFC [#0740](https://rfcs.emberjs.com/id/0740-ember-data-deprecate-non-strict-types). \ No newline at end of file diff --git a/content/ember-data/v5/ember-data-deprecate-store-extends-ember-object.md b/content/ember-data/v5/ember-data-deprecate-store-extends-ember-object.md index 32acc9aa..452cb005 100644 --- a/content/ember-data/v5/ember-data-deprecate-store-extends-ember-object.md +++ b/content/ember-data/v5/ember-data-deprecate-store-extends-ember-object.md @@ -3,6 +3,7 @@ title: Store will no longer extend EmberObject in 6.0 until: '6.0' since: '5.4' displayId: ember-data:deprecate-store-extends-ember-object +rfc: https://rfcs.emberjs.com/id/1026-ember-data-deprecate-store-extends-ember-object --- The Store class extending from EmberObject is deprecated and the class will no @@ -28,4 +29,4 @@ If you are unsure whether your Store class uses EmberObject APIs, set this config and uses of those APIs will throw exceptions. The most common API that may have been used is `Store.extend({...`. -This deprecation is from RFC [#1026](https://rfcs.emberjs.com/id/1026-ember-data-deprecate-store-extends-ember-object). +This deprecation was introduced in RFC [#1026](https://rfcs.emberjs.com/id/1026-ember-data-deprecate-store-extends-ember-object).