@warp-drive/legacy 5.8.0-alpha.4 → 5.8.0-alpha.40

package/declarations/model-fragments/utilities/with-array-defaults.d.ts

@@ -0,0 +1,15 @@
+/**
+* Used as a helper to setup the relevant parts of an array
+* schema and add extensions etc.
+*
+* @param arrayName The name of the array
+* @returns The schema for an array
+*/
+export declare function withArrayDefaults<ArrayName extends string>(arrayName: ArrayName): {
+	kind: "array";
+	name: ArrayName;
+	type: `array:${string}`;
+	options: {
+		arrayExtensions: string[];
+	};
+};

package/declarations/model-fragments/utilities/with-fragment-array-defaults.d.ts

@@ -0,0 +1,20 @@
+/**
+* Used as a helper to setup the relevant parts of a fragment-array
+* schema and add extensions etc.
+*
+* @param fragmentArrayType The type of the fragment-array
+* @param fragmentArrayName The name of the fragment-array
+* @returns The schema for a fragment-array
+*/
+export declare function withFragmentArrayDefaults<
+	FragmentArrayType extends string,
+	FragmentArrayName extends string
+>(fragmentArrayType: FragmentArrayType, fragmentArrayName?: FragmentArrayName): {
+	kind: "schema-array";
+	type: `fragment:${string}`;
+	name: string;
+	options: {
+		arrayExtensions: string[];
+		defaultValue: boolean;
+	};
+};

package/declarations/model-fragments/utilities/with-fragment-defaults.d.ts

@@ -0,0 +1,19 @@
+/**
+* Used as a helper to setup the relevant parts of a fragment schema
+* and add extensions etc.
+*
+* @param fragmentType The type of the fragment
+* @param fragmentName The optional name of the fragment. If not provided, it will default to the fragmentType.
+* @returns The schema for a fragment
+*/
+export declare function withFragmentDefaults<
+	FragmentType extends string,
+	FragmentName extends string
+>(fragmentType: FragmentType, fragmentName?: FragmentName): {
+	kind: "schema-object";
+	type: `fragment:${FragmentType}`;
+	name: FragmentType | FragmentName;
+	options: {
+		objectExtensions: string[];
+	};
+};

package/declarations/model-fragments/utilities/with-legacy.d.ts

@@ -0,0 +1,3 @@
+import type { LegacyResourceSchema, ResourceSchema } from "@warp-drive/core/types/schema/fields";
+import type { WithPartial } from "@warp-drive/core/types/utils";
+export declare function withLegacy(schema: WithPartial<LegacyResourceSchema, "legacy" | "identity">): ResourceSchema;

package/declarations/model-fragments.d.ts

@@ -0,0 +1,9 @@
+export { withArrayDefaults } from "./model-fragments/utilities/with-array-defaults.js";
+export { withFragmentDefaults } from "./model-fragments/utilities/with-fragment-defaults.js";
+export { withFragmentArrayDefaults } from "./model-fragments/utilities/with-fragment-array-defaults.js";
+export { withLegacy } from "./model-fragments/utilities/with-legacy.js";
+export { registerFragmentExtensions } from "./model-fragments/instance-initializers/fragment-extensions.js";
+export { modelFor } from "./model-fragments/hooks/model-for.js";
+export { FragmentArray, FragmentArrayExtension } from "./model-fragments/extensions/fragment-array.js";
+export { Fragment, FragmentExtension } from "./model-fragments/extensions/fragment.js";
+export type { WithFragment, WithFragmentArray } from "./model-fragments/index.js";

package/declarations/model.d.ts

@@ -1,7 +1,7 @@
 /**
 * This package provides a Presentation Model for resource data in an WarpDrive Cache.
 *
-* Models are defined as classes extending from `import Model from '@ember-data/model';` and the
+* Models are defined as classes extending from `import Model from '@warp-drive/legacy/model';` and the
 * attributes and relationships on these classes are parsed at runtime to supply static "schema"
 * to WarpDrive's SchemaService.
 *
@@ -17,7 +17,7 @@ the resource data for a given `type` and `id`.
 ### Defining a Model
 
 ```js [app/models/person.js]
-import Model, { attr, belongsTo, hasMany } from '@ember-data/model';
+import Model, { attr, belongsTo, hasMany } from '@warp-drive/legacy/model';
 
 export default class PersonModel extends Model {
 @attr name;

package/declarations/serializer/-private/embedded-records-mixin.d.ts

@@ -14,7 +14,7 @@ Note also that this mixin does not work with JSONAPISerializer because the JSON:
 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 = {
@@ -85,11 +85,6 @@ instances must have an `id` property to be used with Ember Data.
 are. Please read the docs for the methods this mixin provides, in case you need
 to modify it to fit your specific needs.**
 
-For example, review the docs for each method of this mixin:
-* [normalize](/ember-data/release/classes/EmbeddedRecordsMixin/methods/normalize?anchor=normalize)
-* [serializeBelongsTo](/ember-data/release/classes/EmbeddedRecordsMixin/methods/serializeBelongsTo?anchor=serializeBelongsTo)
-* [serializeHasMany](/ember-data/release/classes/EmbeddedRecordsMixin/methods/serializeHasMany?anchor=serializeHasMany)
-
 @class EmbeddedRecordsMixin
 @public
 */

package/declarations/serializer/-private/transforms/boolean.d.ts

@@ -5,8 +5,8 @@ export interface BooleanTransform {
 /**
 The `BooleanTransform` class is used to serialize and deserialize
 boolean attributes on Ember Data record objects. This transform is
-used when `boolean` is passed as the type parameter to the
-[attr](/ember-data/release/functions/@ember-data%2Fmodel/attr) function.
+used when `'boolean'` is passed as the type parameter to the
+{@link attr}function.
 
 Usage
 

package/declarations/serializer/-private/transforms/date.d.ts

@@ -5,8 +5,8 @@ export interface DateTransform {
 /**
 The `DateTransform` class is used to serialize and deserialize
 date attributes on Ember Data record objects. This transform is used
-when `date` is passed as the type parameter to the
-[attr](/ember-data/release/functions/@ember-data%2Fmodel/attr) function. It uses the [`ISO 8601`](https://en.wikipedia.org/wiki/ISO_8601)
+when `'date'` is passed as the type parameter to the
+{@link attr} function. It uses the [`ISO 8601`](https://en.wikipedia.org/wiki/ISO_8601)
 standard.
 
 ```js [app/models/score.js]

package/declarations/serializer/-private/transforms/number.d.ts

@@ -6,7 +6,7 @@ export interface NumberTransform {
 The `NumberTransform` class is used to serialize and deserialize
 numeric attributes on Ember Data record objects. This transform is
 used when `number` is passed as the type parameter to the
-[attr](/ember-data/release/functions/@ember-data%2Fmodel/attr) function.
+{@link attr} function.
 
 Usage
 

package/declarations/serializer/-private/transforms/string.d.ts

@@ -6,7 +6,7 @@ export interface StringTransform {
 The `StringTransform` class is used to serialize and deserialize
 string attributes on Ember Data record objects. This transform is
 used when `string` is passed as the type parameter to the
-[attr](/ember-data/release/functions/@ember-data%2Fmodel/attr) function.
+{@link attr} function.
 
 Usage
 

package/declarations/serializer/json-api.d.ts

@@ -1,13 +1,11 @@
 /**
-* <blockquote style="margin: 1em; padding: .1em 1em .1em 1em; border-left: solid 1em #E34C32; background: #e0e0e0;">
-<p>
+* :::danger
 ⚠️ <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 adapter, 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
-</p>
-</blockquote>
+{@link Handler} instead to be used with the {@link RequestManager}
+:::
 
-In EmberData a Serializer is used to serialize and deserialize
+In WarpDrive a Serializer is used to serialize and deserialize
 records when they are transferred in and out of an external source.
 This process involves normalizing property names, transforming
 attribute values and serializing relationships.
@@ -18,7 +16,7 @@ serializer recommended by Ember Data.
 This serializer normalizes a JSON API payload that looks like:
 
 ```js [app/models/player.js]
-import Model, { attr, belongsTo } from '@ember-data/model';
+import Model, { attr, belongsTo } from '@warp-drive/legacy/model';
 
 export default class Player extends Model {
 @attr('string') name;
@@ -29,7 +27,7 @@ export default class Player extends Model {
 ```
 
 ```js [app/models/club.js]
-import Model, { attr, hasMany } from '@ember-data/model';
+import Model, { attr, hasMany } from '@warp-drive/legacy/model';
 
 export default class Club extends Model {
 @attr('string') name;
@@ -94,7 +92,7 @@ below shows how this could be done using `normalizeArrayResponse` and
 `extractRelationship`.
 
 ```js [app/serializers/application.js]
-import JSONAPISerializer from '@ember-data/serializer/json-api';
+import JSONAPISerializer from '@warp-drive/legacy/serializer/json-api';
 
 export default class ApplicationSerializer extends JSONAPISerializer {
 normalizeArrayResponse(store, primaryModelClass, payload, id, requestType) {

package/declarations/serializer/json.d.ts

@@ -1,18 +1,16 @@
 /**
-* <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.
+* :::danger
+⚠️ **This is LEGACY documentation** for a feature that is no longer encouraged to be used.
 If starting a new app or thinking of implementing a new adapter, 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
-</p>
-</blockquote>
+{@link Handler} instead to be used with the {@link RequestManager}
+:::
 
-In EmberData a Serializer is used to serialize and deserialize
+In WarpDrive a Serializer is used to serialize and deserialize
 records when they are transferred in and out of an external source.
 This process involves normalizing property names, transforming
 attribute values and serializing relationships.
 
-By default, EmberData uses and recommends the `JSONAPISerializer`.
+By default, WarpDrive uses and recommends the `JSONAPISerializer`.
 
 `JSONSerializer` is useful for simpler or legacy backends that may
 not support the http://jsonapi.org/ spec.
@@ -20,7 +18,7 @@ not support the http://jsonapi.org/ spec.
 For example, given the following `User` model and JSON payload:
 
 ```js [app/models/user.js]
-import Model, { attr, belongsTo, hasMany } from '@ember-data/model';
+import Model, { attr, belongsTo, hasMany } from '@warp-drive/legacy/model';
 
 export default class UserModel extends Model {
 @hasMany('user') friends;

package/declarations/serializer/rest.d.ts

@@ -1,11 +1,9 @@
 /**
-* <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.
+* :::danger
+⚠️ **This is LEGACY documentation** for a feature that is no longer encouraged to be used.
 If starting a new app or thinking of implementing a new adapter, 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
-</p>
-</blockquote>
+{@link Handler} instead to be used with the {@link RequestManager}
+:::
 
 Normally, applications will use the `RESTSerializer` by implementing
 the `normalize` method.

package/declarations/serializer.d.ts

@@ -1,13 +1,11 @@
 /**
 ## 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.
+:::danger
+⚠️ **This is LEGACY documentation** 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
-</p>
-</blockquote>
+{@link Handler} instead to be used with the {@link RequestManager}
+:::
 
 In order to properly manage and present your data, WarpDrive
 needs to understand the structure of data it receives.
@@ -16,14 +14,14 @@ needs to understand the structure of data it receives.
 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.
 
@@ -69,7 +67,7 @@ store.serializerFor('author');
 //   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`.
 
@@ -93,7 +91,7 @@ Any serializer in `app/serializers/` can be looked up by `name` using `store.ser
 ### 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 +122,7 @@ And you can optionally override the following methods:
 
 * `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/{-private-8UmnAf9J.js → -private-B1pSSN52.js}

@@ -1202,7 +1202,7 @@ function _flushPendingSave(store, pending) {
 
 /**
  * Utilities - often temporary - for maintaining backwards compatibility with
- * older parts of EmberData.
+ * older parts of WarpDrive.
  *
   @module
 */

package/dist/adapter/-private.js

@@ -1 +1 @@
-export { d as determineBodyPromise, g as fetch, p as parseResponseHeaders, b as serializeIntoHash, s as serializeQueryParams, a as setupFastboot } from "../serialize-into-hash-CS0MIv4F.js";
+export { d as determineBodyPromise, g as fetch, p as parseResponseHeaders, b as serializeIntoHash, s as serializeQueryParams, a as setupFastboot } from "../serialize-into-hash-BnYvPex3.js";

package/dist/adapter/error.js

@@ -3,17 +3,16 @@ import { macroCondition, getGlobalConfig } from '@embroider/macros';
 
 /* eslint-disable @typescript-eslint/no-unsafe-assignment */
 /* eslint-disable @typescript-eslint/no-unsafe-member-access */
+// eslint-disable-next-line @typescript-eslint/no-unused-vars
 
 /**
   ## 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.
+  :::danger
+    ⚠️ **This is LEGACY documentation** for a feature that is no longer encouraged to be used.
     If starting a new app or thinking of implementing a new adapter, 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
-  </p>
-  </blockquote>
+    {@link Handler} instead to be used with the {@link RequestManager}
+  :::
 
   An `AdapterError` is used by an adapter to signal that an error occurred
   during a request to an external API. It indicates a generic error, and
@@ -25,7 +24,7 @@ import { macroCondition, getGlobalConfig } from '@embroider/macros';
   it was closed for maintenance:
 
   ```js [app/adapters/maintenance-error.js]
-  import AdapterError from '@ember-data/adapter/error';
+  import AdapterError from '@warp-drive/legacy/adapter/error';
 
   export default AdapterError.extend({ message: "Down for maintenance." });
   ```
@@ -33,7 +32,7 @@ import { macroCondition, getGlobalConfig } from '@embroider/macros';
   This error would then be returned by an adapter's `handleResponse` method:
 
   ```js [app/adapters/application.js]
-  import JSONAPIAdapter from '@ember-data/adapter/json-api';
+  import JSONAPIAdapter from '@warp-drive/legacy/adapter/json-api';
   import MaintenanceError from './maintenance-error';
 
   export default class ApplicationAdapter extends JSONAPIAdapter {
@@ -147,8 +146,8 @@ function extend(ParentErrorClass, defaultMessage) {
 
   ```js [app/adapters/post.js]
   import RSVP from 'RSVP';
-  import RESTAdapter from '@ember-data/adapter/rest';
-  import { InvalidError } from '@ember-data/adapter/error';
+  import RESTAdapter from '@warp-drive/legacy/adapter/rest';
+  import { InvalidError } from '@warp-drive/legacy/adapter/error';
 
   export default class ApplicationAdapter extends RESTAdapter {
     updateRecord() {
@@ -190,7 +189,7 @@ InvalidError.prototype.code = 'InvalidError';
   connection if an adapter operation has timed out:
 
   ```js [app/routes/application.js]
-  import { TimeoutError } from '@ember-data/adapter/error';
+  import { TimeoutError } from '@warp-drive/legacy/adapter/error';
 
   export default class ApplicationRoute extends Route {
     @action
@@ -236,7 +235,7 @@ AbortError.prototype.code = 'AbortError';
   request is unauthorized:
 
   ```js [app/routes/application.js]
-  import { UnauthorizedError } from '@ember-data/adapter/error';
+  import { UnauthorizedError } from '@warp-drive/legacy/adapter/error';
 
   export default class ApplicationRoute extends Route {
     @action
@@ -282,7 +281,7 @@ ForbiddenError.prototype.code = 'ForbiddenError';
   for a specific model that does not exist. For example:
 
   ```js [app/routes/post.js]
-  import { NotFoundError } from '@ember-data/adapter/error';
+  import { NotFoundError } from '@warp-drive/legacy/adapter/error';
 
   export default class PostRoute extends Route {
     @service store;

package/dist/adapter/json-api.js

@@ -1,8 +1,11 @@
 import { dasherize, pluralize } from '@warp-drive/utilities/string';
 import '@ember/debug';
 import { macroCondition, getGlobalConfig } from '@embroider/macros';
-import { b as serializeIntoHash } from "../serialize-into-hash-CS0MIv4F.js";
+import { b as serializeIntoHash } from "../serialize-into-hash-BnYvPex3.js";
 import { RESTAdapter } from './rest.js';
+
+// eslint-disable-next-line @typescript-eslint/no-unused-vars
+
 class JSONAPIAdapter extends RESTAdapter {
   _defaultContentType = 'application/vnd.api+json';
 

package/dist/adapter/rest.js

@@ -2,7 +2,7 @@ import { getOwner } from '@ember/application';
 import { warn } from '@ember/debug';
 import { computed } from '@ember/object';
 import { Adapter, BuildURLMixin } from '../adapter.js';
-import { b as serializeIntoHash, d as determineBodyPromise, g as getFetchFunction, s as serializeQueryParams, p as parseResponseHeaders } from "../serialize-into-hash-CS0MIv4F.js";
+import { b as serializeIntoHash, d as determineBodyPromise, g as getFetchFunction, s as serializeQueryParams, p as parseResponseHeaders } from "../serialize-into-hash-BnYvPex3.js";
 import { InvalidError, ServerError, ConflictError, NotFoundError, ForbiddenError, UnauthorizedError, AdapterError, TimeoutError, AbortError } from './error.js';
 import { macroCondition, getGlobalConfig } from '@embroider/macros';
 import { d as decorateMethodV2 } from "../runtime-BPCpkOf1-BKOwiRJp.js";
@@ -14,13 +14,11 @@ import { d as decorateMethodV2 } from "../runtime-BPCpkOf1-BKOwiRJp.js";
 const AdapterWithBuildURLMixin = Adapter.extend(BuildURLMixin);
 
 /**
- * <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.
+ * :::danger
+    ⚠️ **This is LEGACY documentation** for a feature that is no longer encouraged to be used.
     If starting a new app or thinking of implementing a new adapter, 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
-  </p>
-  </blockquote>
+    {@link Handler} instead to be used with the {@link RequestManager}
+  :::
 
   The REST adapter allows your store to communicate with an HTTP server by
   transmitting JSON via XHR.
@@ -392,8 +390,7 @@ class RESTAdapter extends AdapterWithBuildURLMixin {
     Some APIs require HTTP headers, e.g. to provide an API
     key. Arbitrary headers can be set as key/value pairs on the
     `RESTAdapter`'s `headers` object and Ember Data will send them
-    along with each ajax request. For dynamic headers see [headers
-    customization](/ember-data/release/classes/RESTAdapter).
+    along with each ajax request..
      ```js [app/adapters/application.js]
     import { RESTAdapter } from '@warp-drive/legacy/adapter/rest';
      export default class ApplicationAdapter extends RESTAdapter {

package/dist/adapter.js

@@ -496,13 +496,11 @@ const BuildURLMixin = Mixin.create(mixinProps);
 /**
  * ## 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.
+ * :::danger
+ *   ⚠️ **This is LEGACY documentation** for a feature that is no longer encouraged to be used.
  *   If starting a new app or thinking of implementing a new adapter, 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/warp-drive-data/warp-drive/tree/main/packages/request#readme">RequestManager</a>
- * </p>
- * </blockquote>
+ *   {@link Handler} instead to be used with the {@link RequestManager}
+ * ::::
  *
  * In order to properly fetch and update data, @warp-drive/legacy
  * needs to understand how to connect to your API.

package/dist/compat/-private.js

@@ -1 +1 @@
-export { F as FetchManager, S as SaveOp, c as Snapshot, b as SnapshotRecordArray, u as upgradeStore } from "../-private-8UmnAf9J.js";
+export { F as FetchManager, S as SaveOp, c as Snapshot, b as SnapshotRecordArray, u as upgradeStore } from "../-private-B1pSSN52.js";

package/dist/compat/builders.js

@@ -9,16 +9,16 @@ import { storeFor, recordIdentifierFor } from '@warp-drive/core';
   When passed to `store.request`, this config will result in the same behavior as a `store.findAll` request.
   Additionally, it takes the same options as `store.findAll`.
 
-  All `@ember-data/legacy-compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
+  All `@warp-drive/legacy/compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
   This is useful for quickly upgrading an entire app to a unified syntax while a longer incremental migration is made to shift off of adapters and serializers.
-  To that end, these builders are deprecated and will be removed in a future version of Ember Data.
+  To that end, these builders are deprecated and will be removed in a future version of WarpDrive.
 
   @deprecated
   @public
-  @param {String} type the name of the resource
-  @param {Object} query a query to be used by the adapter
-  @param {FindAllBuilderOptions} [options] optional, may include `adapterOptions` hash which will be passed to adapter.findAll
-  @return {FindAllRequestInput} request config
+  @param type the name of the resource
+  @param query a query to be used by the adapter
+  @param options optional, may include `adapterOptions` hash which will be passed to adapter.findAll
+  @return request config
 */
 function findAllBuilder(type, options = {}) {
   macroCondition(getGlobalConfig().WarpDrive.env.DEBUG) ? (test => {
@@ -51,7 +51,7 @@ function findAllBuilder(type, options = {}) {
   **Example 1**
 
   ```ts
-  import { findRecord } from '@ember-data/legacy-compat/builders';
+  import { findRecord } from '@warp-drive/legacy/compat/builders';
   const { content: post } = await store.request<Post>(findRecord<Post>('post', '1'));
   ```
 
@@ -62,20 +62,20 @@ function findAllBuilder(type, options = {}) {
   the typical pairing from [JSON:API](https://jsonapi.org/format/#document-resource-object-identification)
 
   ```ts
-  import { findRecord } from '@ember-data/legacy-compat/builders';
+  import { findRecord } from '@warp-drive/legacy/compat/builders';
   const { content: post } = await store.request<Post>(findRecord<Post>({ type: 'post', id }));
   ```
 
-  All `@ember-data/legacy-compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
+  All `@warp-drive/legacy/compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
   This is useful for quickly upgrading an entire app to a unified syntax while a longer incremental migration is made to shift off of adapters and serializers.
-  To that end, these builders are deprecated and will be removed in a future version of Ember Data.
+  To that end, these builders are deprecated and will be removed in a future version of Warp Drive.
 
   @deprecated
   @public
-  @param {string|object} resource - either a string representing the name of the resource or a ResourceIdentifier object containing both the type (a string) and the id (a string) for the record or an lid (a string) of an existing record
-  @param {string|number|object} id - optional object with options for the request only if the first param is a ResourceIdentifier, else the string id of the record to be retrieved
-  @param {FindRecordBuilderOptions} [options] - if the first param is a string this will be the optional options for the request. See examples for available options.
-  @return {FindRecordRequestInput} request config
+  @param resource - either a string representing the name of the resource or a ResourceIdentifier object containing both the type (a string) and the id (a string) for the record or an lid (a string) of an existing record
+  @param id - optional object with options for the request only if the first param is a ResourceIdentifier, else the string id of the record to be retrieved
+  @param options - if the first param is a string this will be the optional options for the request. See examples for available options.
+  @return request config
 */
 function findRecordBuilder(resource, idOrOptions, options) {
   macroCondition(getGlobalConfig().WarpDrive.env.DEBUG) ? (test => {
@@ -118,16 +118,16 @@ function findRecordBuilder(resource, idOrOptions, options) {
   When passed to `store.request`, this config will result in the same behavior as a `store.query` request.
   Additionally, it takes the same options as `store.query`.
 
-  All `@ember-data/legacy-compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
+  All `@warp-drive/legacy/compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
   This is useful for quickly upgrading an entire app to a unified syntax while a longer incremental migration is made to shift off of adapters and serializers.
-  To that end, these builders are deprecated and will be removed in a future version of Ember Data.
+  To that end, these builders are deprecated and will be removed in a future version of WarpDrive.
 
   @deprecated
   @public
-  @param {String} type the name of the resource
-  @param {Object} query a query to be used by the adapter
-  @param {QueryBuilderOptions} [options] optional, may include `adapterOptions` hash which will be passed to adapter.query
-  @return {QueryRequestInput} request config
+  @param type the name of the resource
+  @param query a query to be used by the adapter
+  @param options optional, may include `adapterOptions` hash which will be passed to adapter.query
+  @return request config
 */
 function queryBuilder(type, query, options = {}) {
   macroCondition(getGlobalConfig().WarpDrive.env.DEBUG) ? (test => {
@@ -163,16 +163,16 @@ function queryBuilder(type, query, options = {}) {
   When passed to `store.request`, this config will result in the same behavior as a `store.queryRecord` request.
   Additionally, it takes the same options as `store.queryRecord`.
 
-  All `@ember-data/legacy-compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
+  All `@warp-drive/legacy/compat` builders exist to enable you to migrate your codebase to using the correct syntax for `store.request` while temporarily preserving legacy behaviors.
   This is useful for quickly upgrading an entire app to a unified syntax while a longer incremental migration is made to shift off of adapters and serializers.
-  To that end, these builders are deprecated and will be removed in a future version of Ember Data.
+  To that end, these builders are deprecated and will be removed in a future version of WarpDrive.
 
   @deprecated
   @public
-  @param {String} type the name of the resource
-  @param {Object} query a query to be used by the adapter
-  @param {QueryBuilderOptions} [options] optional, may include `adapterOptions` hash which will be passed to adapter.query
-  @return {QueryRecordRequestInput} request config
+  @param type the name of the resource
+  @param query a query to be used by the adapter
+  @param options optional, may include `adapterOptions` hash which will be passed to adapter.query
+  @return request config
 */
 
 function queryRecordBuilder(type, query, options) {