@warp-drive/legacy 5.8.0-alpha.9 → 5.8.0-beta.1

package/dist/serializer/rest.js

@@ -1,6 +1,6 @@
 import { warn } from '@ember/debug';
 import { camelize, dasherize, singularize } from '@warp-drive/utilities/string';
-import { J as JSONSerializer, c as coerceId } from "../json-ksWOHRfq.js";
+import { J as JSONSerializer, c as coerceId } from "../json-ChdEfB0X.js";
 import { macroCondition, getGlobalConfig } from '@embroider/macros';
 import Mixin from '@ember/object/mixin';
 
@@ -25,7 +25,7 @@ import Mixin from '@ember/object/mixin';
   Below is an example of a per-type serializer (`post` type).
 
   ```js [app/serializers/post.js]
-  import RESTSerializer, { EmbeddedRecordsMixin } from '@ember-data/serializer/rest';
+  import RESTSerializer, { EmbeddedRecordsMixin } from '@warp-drive/legacy/serializer/rest';
 
   export default class PostSerializer extends RESTSerializer.extend(EmbeddedRecordsMixin) {
     attrs = {
@@ -140,7 +140,7 @@ const EmbeddedRecordsMixin = Mixin.create({
     Serialize `belongsTo` relationship when it is configured as an embedded object.
      This example of an author model belongs to a post model:
      ```js
-    import Model, { attr, belongsTo } from '@ember-data/model';
+    import Model, { attr, belongsTo } from '@warp-drive/legacy/model';
      Post = Model.extend({
       title:    attr('string'),
       body:     attr('string'),
@@ -153,7 +153,7 @@ const EmbeddedRecordsMixin = Mixin.create({
     ```
      Use a custom (type) serializer for the post model to configure embedded author
      ```js [app/serializers/post.js]
-    import RESTSerializer, { EmbeddedRecordsMixin } from '@ember-data/serializer/rest';
+    import RESTSerializer, { EmbeddedRecordsMixin } from '@warp-drive/legacy/serializer/rest';
      export default class PostSerializer extends RESTSerializer.extend(EmbeddedRecordsMixin) {
       attrs = {
         author: { embedded: 'always' }
@@ -229,7 +229,7 @@ const EmbeddedRecordsMixin = Mixin.create({
     Serializes `hasMany` relationships when it is configured as embedded objects.
      This example of a post model has many comments:
      ```js
-    import Model, { attr, belongsTo, hasMany } from '@ember-data/model';
+    import Model, { attr, belongsTo, hasMany } from '@warp-drive/legacy/model';
      Post = Model.extend({
       title:    attr('string'),
       body:     attr('string'),
@@ -242,7 +242,7 @@ const EmbeddedRecordsMixin = Mixin.create({
     ```
      Use a custom (type) serializer for the post model to configure embedded comments
      ```js [app/serializers/post.js]
-    import RESTSerializer, { EmbeddedRecordsMixin } from '@ember-data/serializer/rest';
+    import RESTSerializer, { EmbeddedRecordsMixin } from '@warp-drive/legacy/serializer/rest';
      export default class PostSerializer extends RESTSerializer.extend(EmbeddedRecordsMixin) {
       attrs = {
         comments: { embedded: 'always' }
@@ -274,7 +274,7 @@ const EmbeddedRecordsMixin = Mixin.create({
     `{ serialize: 'records', deserialize: 'records' }`
      To embed the `ids` for a related object (using a hasMany relationship):
      ```js [app/serializers/post.js]
-    import RESTSerializer, { EmbeddedRecordsMixin } from '@ember-data/serializer/rest';
+    import RESTSerializer, { EmbeddedRecordsMixin } from '@warp-drive/legacy/serializer/rest';
      export default class PostSerializer extends RESTSerializer.extend(EmbeddedRecordsMixin) {
       attrs = {
         comments: { serialize: 'ids', deserialize: 'records' }
@@ -312,7 +312,7 @@ const EmbeddedRecordsMixin = Mixin.create({
     });
     ```
      ```js [app/serializers/user.js]
-    import RESTSerializer, { EmbeddedRecordsMixin } from '@ember-data/serializer/rest';
+    import RESTSerializer, { EmbeddedRecordsMixin } from '@warp-drive/legacy/serializer/rest';
      export default class UserSerializer extends RESTSerializer.extend(EmbeddedRecordsMixin) {
       attrs = {
         pets: { serialize: 'ids-and-types', deserialize: 'records' }
@@ -951,7 +951,7 @@ const RESTSerializer = JSONSerializer.extend({
     the name of the model in your app. Let's take a look at an example model,
     and an example payload:
      ```js [app/models/post.js]
-    import Model from '@ember-data/model';
+    import Model from '@warp-drive/legacy/model';
      export default class Post extends Model {}
     ```
      ```javascript
@@ -1000,7 +1000,7 @@ const RESTSerializer = JSONSerializer.extend({
     each attribute and belongsTo relationship.
      For example, consider this model:
      ```js [app/models/comment.js]
-    import Model, { attr, belongsTo } from '@ember-data/model';
+    import Model, { attr, belongsTo } from '@warp-drive/legacy/model';
      export default class Comment extends Model {
       @attr title
       @attr body

package/dist/serializer.js

@@ -18,14 +18,14 @@ import { a as decorateFieldV2, i as initializeDeferredDecorator } from "./runtim
   the format WarpDrive understands.
 
   Data received from an API response is **normalized** into
-  [JSON:API](https://jsonapi.org/) (the format used internally
+  [{json:api}](https://jsonapi.org/) (the format used internally
   by WarpDrive), while data sent to an API is **serialized**
   into the format the API expects.
 
   ### Implementing a Serializer
 
   There are only two required serializer methods, one for
-  normalizing data from the server API format into JSON:API, and
+  normalizing data from the server API format into {json:api}, and
   another for serializing records via `Snapshots` into the expected
   server API format.
 
@@ -71,7 +71,7 @@ import { a as decorateFieldV2, i as initializeDeferredDecorator } from "./runtim
   //   app/serializers/application.js
   ```
 
-  Most requests in @warp-drive/legacy are made with respect to a particular `type` (or `modelName`)
+  Most requests in `@warp-drive/legacy` are made with respect to a particular `type` (or `modelName`)
   (e.g., "get me the full collection of **books**" or "get me the **employee** whose id is 37"). We
   refer to this as the **primary** resource `type`.
 
@@ -95,7 +95,7 @@ import { a as decorateFieldV2, i as initializeDeferredDecorator } from "./runtim
   ### Default Serializers
 
   For applications whose APIs are *very close to* or *exactly* the **REST** format or **JSON:API**
-  format the `@ember-data/serializer` package contains implementations these applications can
+  format the `@warp-drive/legacy/serializer` package contains implementations these applications can
   extend. It also contains a simple `JSONSerializer` for serializing to/from very basic JSON objects.
 
   Many applications will find writing their own serializer to be more performant and less
@@ -124,8 +124,7 @@ const service = s.service ?? s.inject;
 
     * `normalize()`
 
-  For an example implementation, see
-  [JSONSerializer](JSONSerializer), the included JSON serializer.
+  For an example implementation, see the included {@link JSONSerializer}.
 
   @class Serializer
   @public

package/dist/store.js

@@ -1,7 +1,8 @@
-import { defineSignal, assertPrivateStore, ensureStringId, recordIdentifierFor, constructResource, storeFor } from '@warp-drive/core/store/-private';
+import { assertPrivateStore, ensureStringId, recordIdentifierFor, constructResource, storeFor } from '@warp-drive/core/store/-private';
 import { SkipCache } from '@warp-drive/core/types/request';
 import { i as isMaybeIdentifier } from "./utils-Cqw9eRj5.js";
 import { n as normalizeModelName } from "./util-Dul6TZts.js";
+import { defineSignal } from '@warp-drive/core/signals/-leaked';
 import { getOrSetGlobal } from '@warp-drive/core/types/-private';
 import { macroCondition, getGlobalConfig } from '@embroider/macros';