@warp-drive/legacy 5.8.0-alpha.30 → 5.8.0-alpha.32

package/declarations/adapter/error.d.ts

@@ -42,8 +42,8 @@ rejects with a `InvalidError` object that looks like this:
 
 ```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() {
@@ -82,7 +82,7 @@ An example use case would be to warn the user to check their internet
 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
@@ -124,7 +124,7 @@ An example use case would be to redirect the user to a login route if a
 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
@@ -166,7 +166,7 @@ An example use case would be to detect if the user has entered a route
 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/declarations/adapter/json-api.d.ts

@@ -118,7 +118,7 @@ Endpoint paths can be prefixed with a `namespace` by setting the
 namespace property on the adapter:
 
 ```js [app/adapters/application.js]
-import JSONAPIAdapter from '@ember-data/adapter/json-api';
+import JSONAPIAdapter from '@warp-drive/legacy/adapter/json-api';
 
 export default class ApplicationAdapter extends JSONAPIAdapter {
 namespace = 'api/1';
@@ -131,7 +131,7 @@ Requests for the `person` model would now target `/api/1/people/1`.
 An adapter can target other hosts by setting the `host` property.
 
 ```js [app/adapters/application.js]
-import JSONAPIAdapter from '@ember-data/adapter/json-api';
+import JSONAPIAdapter from '@warp-drive/legacy/adapter/json-api';
 
 export default class ApplicationAdapter extends JSONAPIAdapter {
 host = 'https://api.example.com';

package/declarations/compat/builders/find-all.d.ts

@@ -19,16 +19,16 @@ This function builds a request config to perform a `findAll` request for the giv
 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
 */
 export declare function findAllBuilder<T extends TypedRecordInstance>(type: TypeFromInstance<T>, options?: FindAllBuilderOptions): FindAllRequestInput<TypeFromInstance<T>, T[]>;
 export declare function findAllBuilder(type: string, options?: FindAllBuilderOptions): FindAllRequestInput;

package/declarations/compat/builders/find-record.d.ts

@@ -23,7 +23,7 @@ Additionally, it takes the same options as `store.findRecord`, with the exceptio
 **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'));
 ```
 
@@ -34,20 +34,20 @@ of `type` (modelName) and `id` as separate arguments. You may recognize this com
 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
 */
 export declare function findRecordBuilder<T extends TypedRecordInstance>(type: TypeFromInstance<T>, id: string, options?: FindRecordBuilderOptions): FindRecordRequestInput<TypeFromInstance<T>, T>;
 export declare function findRecordBuilder(type: string, id: string, options?: FindRecordBuilderOptions): FindRecordRequestInput;

package/declarations/compat/builders/query.d.ts

@@ -20,16 +20,16 @@ This function builds a request config for a given type and query object.
 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
 */
 export declare function queryBuilder<T extends TypedRecordInstance>(type: TypeFromInstance<T>, query: LegacyResourceQuery, options?: QueryBuilderOptions): QueryRequestInput<TypeFromInstance<T>, T[]>;
 export declare function queryBuilder(type: string, query: LegacyResourceQuery, options?: QueryBuilderOptions): QueryRequestInput;
@@ -50,16 +50,16 @@ This function builds a request config for a given type and query object.
 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
 */
 export declare function queryRecordBuilder<T extends TypedRecordInstance>(type: TypeFromInstance<T>, query: LegacyResourceQuery, options?: QueryBuilderOptions): QueryRecordRequestInput<TypeFromInstance<T>, T | null>;
 export declare function queryRecordBuilder(type: string, query: LegacyResourceQuery, options?: QueryBuilderOptions): QueryRecordRequestInput;

package/declarations/compat.d.ts

@@ -107,7 +107,7 @@ All objects should be in the format expected by the
 serializer.
 
 ```js [app/serializers/application.js]
-import RESTSerializer from '@ember-data/serializer/rest';
+import RESTSerializer from '@warp-drive/legacy/serializer/rest';
 
 export default class ApplicationSerializer extends RESTSerializer;
 ```
@@ -132,13 +132,13 @@ Alternatively, `pushPayload` will accept a model type which
 will determine which serializer will process the payload.
 
 ```js [app/serializers/application.js]
-import RESTSerializer from '@ember-data/serializer/rest';
+import RESTSerializer from '@warp-drive/legacy/serializer/rest';
 
 export default class ApplicationSerializer extends RESTSerializer;
 ```
 
 ```js [app/serializers/post.js]
-import JSONSerializer from '@ember-data/serializer/json';
+import JSONSerializer from '@warp-drive/legacy/serializer/json';
 
 export default JSONSerializer;
 ```

package/declarations/model/-private/references/belongs-to.d.ts

@@ -10,11 +10,11 @@ A `BelongsToReference` is a low-level API that allows access
 and manipulation of a belongsTo relationship.
 
 It is especially useful when you're dealing with `async` relationships
-from `@ember-data/model` as it allows synchronous access to
+from `@warp-drive/legacy/model` as it allows synchronous access to
 the relationship data if loaded, as well as APIs for loading, reloading
 the data or accessing available information without triggering a load.
 
-It may also be useful when using `sync` relationships with `@ember-data/model`
+It may also be useful when using `sync` relationships with `@warp-drive/legacy/model`
 that need to be loaded/reloaded with more precise timing than marking the
 relationship as `async` and relying on autofetch would have allowed.
 
@@ -206,7 +206,7 @@ export default class BelongsToReference<
 	Example
 	
 	```js [app/models/post.js]
-	import Model, { hasMany } from '@ember-data/model';
+	import Model, { hasMany } from '@warp-drive/legacy/model';
 	
 	export default class PostModel extends Model {
 	@hasMany('comment', { async: true, inverse: null }) comments;
@@ -430,7 +430,7 @@ export default class BelongsToReference<
 	});
 	```
 	```js [app/adapters/user.js]
-	import Adapter from '@ember-data/adapter';
+	import Adapter from '@warp-drive/legacy/adapter';
 	
 	export default class UserAdapter extends Adapter {
 	findRecord(store, type, id, snapshot) {

package/declarations/model/-private/references/has-many.d.ts

@@ -19,11 +19,11 @@ A `HasManyReference` is a low-level API that allows access
 and manipulation of a hasMany relationship.
 
 It is especially useful when you're dealing with `async` relationships
-from `@ember-data/model` as it allows synchronous access to
+from `@warp-drive/legacy/model` as it allows synchronous access to
 the relationship data if loaded, as well as APIs for loading, reloading
 the data or accessing available information without triggering a load.
 
-It may also be useful when using `sync` relationships with `@ember-data/model`
+It may also be useful when using `sync` relationships with `@warp-drive/legacy/model`
 that need to be loaded/reloaded with more precise timing than marking the
 relationship as `async` and relying on autofetch would have allowed.
 

package/declarations/model/migration-support.d.ts

@@ -56,14 +56,14 @@ interface LegacyModeRecord<T extends TypedRecordInstance> {
 }
 /**
 * A Type utility that enables quickly adding type information for the fields
-* defined by `import { withDefaults } from '@ember-data/model/migration-support'`.
+* defined by `import { withDefaults } from '@warp-drive/legacy/model/migration-support'`.
 *
 * Example:
 *
 * ```ts
-* import { withDefaults, WithLegacy } from '@ember-data/model/migration-support';
-* import { Type } from '@warp-drive/core-types/symbols';
-* import type { HasMany } from '@ember-data/model';
+* import { withDefaults, WithLegacy } from '@warp-drive/legacy/model/migration-support';
+* import { Type } from '@warp-drive/core/types/symbols';
+* import type { HasMany } from '@@warp-drive/legacy/model';
 *
 * export const UserSchema = withDefaults({
 *   type: 'user',
@@ -99,14 +99,14 @@ export type WithLegacy<T extends TypedRecordInstance> = T & LegacyModeRecord<T>;
 /**
 * A function which adds the necessary fields to a schema and marks it as
 * being in LegacyMode. This is used to support the legacy features of
-* @ember-data/model while migrating to WarpDrive.
+* @warp-drive/legacy/model while migrating to WarpDrive.
 *
 * Example:
 *
 * ```ts
-* import { withDefaults, WithLegacy } from '@ember-data/model/migration-support';
-* import { Type } from '@warp-drive/core-types/symbols';
-* import type { HasMany } from '@ember-data/model';
+* import { withDefaults, WithLegacy } from '@warp-drive/legacy/model/migration-support';
+* import { Type } from '@warp-drive/core/types/symbols';
+* import type { HasMany } from '@warp-drive/legacy/model';
 *
 * export const UserSchema = withDefaults({
 *   type: 'user',
@@ -141,26 +141,42 @@ export type WithLegacy<T extends TypedRecordInstance> = T & LegacyModeRecord<T>;
 * it requires with the schema service.
 *
 * ```ts
-* import { registerDerivations } from '@ember-data/model/migration-support';
+* import { registerDerivations } from '@warp-drive/legacy/model/migration-support';
 *
 * registerDerivations(schema);
 * ```
 *
-* @param {LegacyResourceSchema} schema The schema to add legacy support to.
-* @return {LegacyResourceSchema} The schema with legacy support added.
+* @param schema The schema to add legacy support to.
+* @return The schema with legacy support added.
 * @public
 */
 export declare function withDefaults(schema: WithPartial<LegacyResourceSchema, "legacy" | "identity">): LegacyResourceSchema;
-export declare function withRestoredDeprecatedModelRequestBehaviors(schema: WithPartial<LegacyResourceSchema, "legacy" | "identity">): LegacyResourceSchema;
 /**
-* A function which registers the necessary derivations to support
-* the LegacyMode features of @ember-data/model while migrating to WarpDrive.
+* Adds the necessasary fields to the schema for supporting
+* the deprecated request methods on LegacyMode schemas.
 *
-* This must be called in order to use the fields added by:
+* Use this instead of `withDefaults` to add the fields
+* and behaviors necessary to support Model-Like capabilities.
 *
 * ```ts
-* import { withDefaults } from '@ember-data/model/migration-support';
+* import { withRestoredDeprecatedModelRequestBehaviors } from '@warp-drive/legacy/model/migration-support';
+*
+* export const UserSchema = withRestoredDeprecatedModelRequestBehaviors({
+*   type: 'user',
+*   fields: [
+*     { name: 'firstName', kind: 'attribute' },
+*     { name: 'lastName', kind: 'attribute' },
+*   ]
+* });
 * ```
+*/
+export declare function withRestoredDeprecatedModelRequestBehaviors(schema: WithPartial<LegacyResourceSchema, "legacy" | "identity">): LegacyResourceSchema;
+/**
+* A function which registers the necessary derivations to support
+* the LegacyMode features of @warp-drive/legacy/model while migrating to WarpDrive.
+*
+* This must be called in order to use the fields added by {@link withDefaults} or
+* {@link withRestoredDeprecatedModelRequestBehaviors}.
 *
 * @param schema The schema service to register the derivations with.
 * @public
@@ -180,8 +196,8 @@ export declare function registerDerivations(schema: SchemaService): void;
 * provide their own schema information to the application.
 *
 * ```ts
-* import { DelegatingSchemaService } from '@ember-data/model/migration-support';
-* import { SchemaService } from '@warp-drive/schema-record';
+* import { DelegatingSchemaService } from '@warp-drive/legacy/model/migration-support';
+* import { SchemaService } from '@warp-drive/core/reactive';
 *
 * class AppStore extends Store {
 *   createSchemaService() {

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 = {

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

@@ -16,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;
@@ -27,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;
@@ -92,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

@@ -18,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.d.ts

@@ -91,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

package/dist/adapter/error.js

@@ -24,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." });
   ```
@@ -32,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 {
@@ -146,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() {
@@ -189,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
@@ -235,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
@@ -281,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/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) {

package/dist/compat/utils.js

@@ -6,7 +6,6 @@ import { macroCondition, getGlobalConfig } from '@embroider/macros';
   and more consistent use of IDs and types.
 
   @module
-  @deprecated
 */
 
 let MismatchReporter = function () {};

package/dist/compat.js

@@ -931,7 +931,7 @@ function normalize(modelName, payload) {
     serializer.
 
     ```js [app/serializers/application.js]
-    import RESTSerializer from '@ember-data/serializer/rest';
+    import RESTSerializer from '@warp-drive/legacy/serializer/rest';
 
     export default class ApplicationSerializer extends RESTSerializer;
     ```
@@ -956,13 +956,13 @@ function normalize(modelName, payload) {
     will determine which serializer will process the payload.
 
     ```js [app/serializers/application.js]
-    import RESTSerializer from '@ember-data/serializer/rest';
+    import RESTSerializer from '@warp-drive/legacy/serializer/rest';
 
      export default class ApplicationSerializer extends RESTSerializer;
     ```
 
     ```js [app/serializers/post.js]
-    import JSONSerializer from '@ember-data/serializer/json';
+    import JSONSerializer from '@warp-drive/legacy/serializer/json';
 
     export default JSONSerializer;
     ```