npm - @ember-data-types/serializer - Versions diffs - 5.6.0-alpha.15 → 5.6.0-alpha.17 - Mend

@@ -4,112 +4,112 @@
 /// <reference path="./rest.d.ts" />
 declare module '@ember-data/serializer' {
   /**
-    ## Overview
+  ## Overview
-    <blockquote style="margin: 1em; padding: .1em 1em .1em 1em; border-left: solid 1em #E34C32; background: #e0e0e0;">
-    <p>
-      ⚠️ <strong>This is LEGACY documentation</strong> for a feature that is no longer encouraged to be used.
-      If starting a new app or thinking of implementing a new serializer, consider writing a
-      <a href="/ember-data/release/classes/%3CInterface%3E%20Handler">Handler</a> instead to be used with the <a href="https://github.com/emberjs/data/tree/main/packages/request#readme">RequestManager</a>
-    </p>
-    </blockquote>
+  <blockquote style="margin: 1em; padding: .1em 1em .1em 1em; border-left: solid 1em #E34C32; background: #e0e0e0;">
+  <p>
+  ⚠️ <strong>This is LEGACY documentation</strong> for a feature that is no longer encouraged to be used.
+  If starting a new app or thinking of implementing a new serializer, consider writing a
+  <a href="/ember-data/release/classes/%3CInterface%3E%20Handler">Handler</a> instead to be used with the <a href="https://github.com/emberjs/data/tree/main/packages/request#readme">RequestManager</a>
+  </p>
+  </blockquote>
-    In order to properly manage and present your data, EmberData
-    needs to understand the structure of data it receives.
+  In order to properly manage and present your data, EmberData
+  needs to understand the structure of data it receives.
-    `Serializers` convert data between the server's API format and
-    the format EmberData understands.
+  `Serializers` convert data between the server's API format and
+  the format EmberData understands.
-    Data received from an API response is **normalized** into
-    [JSON:API](https://jsonapi.org/) (the format used internally
-    by EmberData), while data sent to an API is **serialized**
-    into the format the API expects.
+  Data received from an API response is **normalized** into
+  [JSON:API](https://jsonapi.org/) (the format used internally
+  by EmberData), while data sent to an API is **serialized**
+  into the format the API expects.
-    ### Implementing a Serializer
+  ### Implementing a Serializer
-    There are only two required serializer methods, one for
-    normalizing data from the server API format into JSON:API, and
-    another for serializing records via `Snapshots` into the expected
-    server API format.
+  There are only two required serializer methods, one for
+  normalizing data from the server API format into JSON:API, and
+  another for serializing records via `Snapshots` into the expected
+  server API format.
-    To implement a serializer, export a class that conforms to the structure
-    described by {@link MinimumSerializerInterface}
-    from the `app/serializers/` directory. An example is below.
+  To implement a serializer, export a class that conforms to the structure
+  described by {@link MinimumSerializerInterface}
+  from the `app/serializers/` directory. An example is below.
-    ```ts
-    import EmberObject from '@ember/object';
+  ```ts
+  import EmberObject from '@ember/object';
-    export default class ApplicationSerializer extends EmberObject {
-      normalizeResponse(store, schema, rawPayload) {
-        return rawPayload;
-      }
+  export default class ApplicationSerializer extends EmberObject {
+  normalizeResponse(store, schema, rawPayload) {
+  return rawPayload;
+  }
-      serialize(snapshot, options) {
-        const serializedResource = {
-          id: snapshot.id,
-          type: snapshot.modelName,
-          attributes: snapshot.attributes()
-        };
+  serialize(snapshot, options) {
+  const serializedResource = {
+  id: snapshot.id,
+  type: snapshot.modelName,
+  attributes: snapshot.attributes()
+  };
-        return serializedResource;
-      }
-    }
-   ```
+  return serializedResource;
+  }
+  }
+  ```
-    ### Serializer Resolution
+  ### Serializer Resolution
-    `store.serializerFor(name)` will lookup serializers defined in
-    `app/serializers/` and return an instance. If no serializer is found, an
-    error will be thrown.
+  `store.serializerFor(name)` will lookup serializers defined in
+  `app/serializers/` and return an instance. If no serializer is found, an
+  error will be thrown.
-    `serializerFor` first attempts to find a serializer with an exact match on `name`,
-    then falls back to checking for the presence of a serializer named `application`.
+  `serializerFor` first attempts to find a serializer with an exact match on `name`,
+  then falls back to checking for the presence of a serializer named `application`.
-    ```ts
-    store.serializerFor('author');
+  ```ts
+  store.serializerFor('author');
-    // lookup paths (in order) =>
-    //   app/serializers/author.js
-    //   app/serializers/application.js
-    ```
+  // lookup paths (in order) =>
+  //   app/serializers/author.js
+  //   app/serializers/application.js
+  ```
-    Most requests in EmberData 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`.
+  Most requests in EmberData 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`.
-    Typically `serializerFor` will be used to find a serializer with a name matching that of the primary
-    resource `type` for the request, falling back to the `application` serializer for those types that
-    do not have a defined serializer. This is often described as a `per-model` or `per-type` strategy
-    for defining serializers. However, because APIs rarely format payloads per-type but rather
-    per-API-version, this may not be a desired strategy.
+  Typically `serializerFor` will be used to find a serializer with a name matching that of the primary
+  resource `type` for the request, falling back to the `application` serializer for those types that
+  do not have a defined serializer. This is often described as a `per-model` or `per-type` strategy
+  for defining serializers. However, because APIs rarely format payloads per-type but rather
+  per-API-version, this may not be a desired strategy.
-    It is recommended that applications define only a single `application` adapter and serializer
-    where possible.
+  It is recommended that applications define only a single `application` adapter and serializer
+  where possible.
-    If you have multiple API formats and the per-type strategy is not viable, one strategy is to
-    write an `application` adapter and serializer that make use of `options` to specify the desired
-    format when making a request.
+  If you have multiple API formats and the per-type strategy is not viable, one strategy is to
+  write an `application` adapter and serializer that make use of `options` to specify the desired
+  format when making a request.
-    ### Using a Serializer
+  ### Using a Serializer
-    Any serializer in `app/serializers/` can be looked up by `name` using `store.serializerFor(name)`.
+  Any serializer in `app/serializers/` can be looked up by `name` using `store.serializerFor(name)`.
-    ### Default Serializers
+  ### 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
-    extend. It also contains a simple `JSONSerializer` for serializing to/from very basic JSON objects.
+  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
+  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
-    complex than extending these classes even when their API format is very close to that expected
-    by these serializers.
+  Many applications will find writing their own serializer to be more performant and less
+  complex than extending these classes even when their API format is very close to that expected
+  by these serializers.
-    It is recommended that apps write their own serializer to best suit the needs of their API and
-    application.
+  It is recommended that apps write their own serializer to best suit the needs of their API and
+  application.
-    @module
+  @module
   */
-  export { Serializer as default } from '@warp-drive/legacy/serializer';
-}
-//# sourceMappingURL=index.d.ts.map
+  export { Serializer as default } from "@warp-drive/legacy/serializer";
+}

@@ -1,6 +1,6 @@
 {
   "name": "@ember-data-types/serializer",
-  "version": "5.6.0-alpha.15",
+  "version": "5.6.0-alpha.17",
   "files": [
     "unstable-preview-types",
     "README.md",

@@ -1,4 +1,4 @@
 declare module '@ember-data/serializer/json-api' {
-  export { JSONAPISerializer as default } from '@warp-drive/legacy/serializer/json-api';
-}
-//# sourceMappingURL=json-api.d.ts.map
+  export { JSONAPISerializer as default } from "@warp-drive/legacy/serializer/json-api";
+}

@@ -1,4 +1,4 @@
 declare module '@ember-data/serializer/json' {
-  export { JSONSerializer as default } from '@warp-drive/legacy/serializer/json';
-}
-//# sourceMappingURL=json.d.ts.map
+  export { JSONSerializer as default } from "@warp-drive/legacy/serializer/json";
+}

@@ -1,4 +1,4 @@
 declare module '@ember-data/serializer/rest' {
-  export { RESTSerializer as default, EmbeddedRecordsMixin } from '@warp-drive/legacy/serializer/rest';
-}
-//# sourceMappingURL=rest.d.ts.map
+  export { RESTSerializer as default, EmbeddedRecordsMixin } from "@warp-drive/legacy/serializer/rest";
+}

@@ -1,4 +1,4 @@
 declare module '@ember-data/serializer/transform' {
-  export { Transform as default, BooleanTransform, StringTransform, NumberTransform, DateTransform, } from '@warp-drive/legacy/serializer/transform';
-}
-//# sourceMappingURL=transform.d.ts.map
+  export { Transform as default, BooleanTransform, StringTransform, NumberTransform, DateTransform } from "@warp-drive/legacy/serializer/transform";
+}

	@@ -1 +0,0 @@
1	- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA0GE;AACF,OAAO,EAAE,UAAU,IAAI,OAAO,EAAE,MAAM,+BAA+B,CAAC"}

	@@ -1 +0,0 @@
1	- {"version":3,"file":"json-api.d.ts","sourceRoot":"","sources":["../src/json-api.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,IAAI,OAAO,EAAE,MAAM,wCAAwC,CAAC"}

	@@ -1 +0,0 @@
1	- {"version":3,"file":"json.d.ts","sourceRoot":"","sources":["../src/json.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,IAAI,OAAO,EAAE,MAAM,oCAAoC,CAAC"}

	@@ -1 +0,0 @@
1	- {"version":3,"file":"rest.d.ts","sourceRoot":"","sources":["../src/rest.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,IAAI,OAAO,EAAE,oBAAoB,EAAE,MAAM,oCAAoC,CAAC"}

	@@ -1 +0,0 @@
1	- {"version":3,"file":"transform.d.ts","sourceRoot":"","sources":["../src/transform.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,SAAS,IAAI,OAAO,EACpB,gBAAgB,EAChB,eAAe,EACf,eAAe,EACf,aAAa,GACd,MAAM,yCAAyC,CAAC"}

@ember-data-types/serializer 5.6.0-alpha.15 → 5.6.0-alpha.17