@ember-data-types/active-record 5.8.0-alpha.40 → 5.8.0-alpha.42

package/README.md

@@ -28,6 +28,12 @@
 
 # @ember-data/active-record
 
+> [!WARNING]
+> **⚠️ This package only exists for backwards compatibility**
+>
+> Newer apps should use [@warp-drive/utilities](https://warp-drive.io/api/@warp-drive/utilities/)
+
+
 This package provides utilities for working with **Active**Record APIs with [***Warp*Drive**](https://warp-drive.io/) when using the older package configuration.
 
 For for modern usage of these utilities, see [@warp-drive/utilities](https://www.npmjs.com/package/@warp-drive/utilities).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ember-data-types/active-record",
-  "version": "5.8.0-alpha.40",
+  "version": "5.8.0-alpha.42",
   "files": [
     "README.md",
     "LICENSE.md",

package/unstable-preview-types/index.d.ts

@@ -1 +1,9 @@
-/// <reference path="./request.d.ts" />
+/// <reference path="./request.d.ts" />
+declare module '@ember-data/active-record' {
+  /**
+  * @module
+  * @mergeModuleWith <project>
+  */
+  export {};
+  
+}

package/unstable-preview-types/request.d.ts

@@ -1,71 +1,4 @@
 declare module '@ember-data/active-record/request' {
-  /**
-  *
-  *
-  *This package provides utilities for working with [ActiveRecord](https://guides.rubyonrails.org/active_record_basics.html#convention-over-configuration-in-active-record) APIs.
-  *
-  * ## Installation
-  *
-  * Install using your javascript package manager of choice. For instance with [pnpm](https://pnpm.io/)
-  *
-  * ::: code-group
-  *
-  * ```sh [pnpm]
-  * pnpm add -E @ember-data/active-record
-  * ```
-  *
-  * ```sh [npm]
-  * npm add -E @ember-data/active-record
-  * ```
-  *
-  * ```sh [yarn]
-  * yarn add -E @ember-data/active-record
-  * ```
-  *
-  * ```sh [bun]
-  * bun add --exact @ember-data/active-record
-  * ```
-  *
-  * :::
-  *
-  * ## Usage
-  *
-  * Request builders are functions that produce [Fetch Options](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).
-  * They take a few contextual inputs about the request you want to make, abstracting away the gnarlier details.
-  *
-  * For instance, to construct a request that would fetch a resource from your API:
-  *
-  * ```ts
-  * import { findRecord } from '@ember-data/active-record/request';
-  *
-  * const options = findRecord('ember-developer', '1', { include: ['pets', 'friends'] });
-  * ```
-  *
-  * This would produce the following request object:
-  *
-  * ```js
-  * {
-  *   url: 'https://api.example.com/v1/ember_developers/1?include=friends,pets',
-  *   method: 'GET',
-  *   headers: <Headers>, // 'Accept': 'application/json;charset=utf-8'
-  *   op: 'findRecord';
-  *   records: [{ type: 'ember-developer', id: '1' }]
-  * }
-  * ```
-  *
-  * Request builder output may be used with either `requestManager.request` or `store.request`.
-  *
-  * ```ts
-  * const data = await store.request(options);
-  * ```
-  *
-  * URLs are stable. The same query will produce the same URL every time, even if the order of keys in
-  * the query or values in an array changes.
-  *
-  * URLs follow the most common ActiveRecord format (underscored pluralized resource types).
-  *
-  * @module
-  */
   export { findRecord, query, deleteRecord, createRecord, updateRecord } from "@warp-drive/utilities/active-record";
   
 }