@warp-drive-mirror/core 5.10.0-alpha.13 → 5.10.0-alpha.14

package/dist/reactive.d.ts

@@ -1,2 +1,277 @@
-import { C as getRequestState, Cn as Transformation, D as ResolvedPromise, Dt as ReactiveDataDocument, E as RejectedPromise, En as withDefaults, H as checkout, K as LegacyManyArray, O as getPromiseState, Ot as ReactiveDocument, R as instantiateRecord, S as ResolvedRequest, Sn as SchemaService, T as PromiseState, Tn as registerDerivations, U as commit, V as ReactiveResource, _ as CancelledRequest, b as RequestLoadingState, bn as ExtensionDef, c as AutorefreshBehaviorCombos, dt as LegacyQueryArray, f as RecoveryFeatures, ft as LegacyLiveArray, g as createRequestSubscription, gt as Checkout, h as SubscriptionArgs, kt as ReactiveErrorDocument, l as AutorefreshBehaviorType, m as RequestSubscription, mt as ReactiveResourceArray, p as RequestArgs, u as ContentFeatures, v as PendingRequest, vn as CAUTION_MEGA_DANGER_ZONE_Extension, w as PendingPromise, wn as fromIdentity, x as RequestState, xn as ProcessedExtension, y as RejectedRequest, z as teardownRecord } from "./internal-CgOlgOt3.js";
+/**
+ * # About
+ *
+ * This module provides an implementation of reactive objects that a Store may use for creating
+ * reactive representations of the raw data for requests, resources and their relationships
+ * stored in the cache.
+ *
+ * - For configuring the store to use these reactive objects, see [The Setup Guide](/guides/configuration/)
+ * - For defining resource schemas, see [The Schema Guide](/guides/the-manual/schemas/)
+ *
+ * Any method that returns a record instance will use the `instantiateRecord`
+ * hook configured above to instantiate a ReactiveResource once this is in place.
+ * After that, its up to you what ReactiveResource can do.
+ *
+ * ## Modes
+ *
+ * ReactiveResource has two modes: `legacy` and `polaris`.
+ *
+ * **LegacyMode** can be used to emulate the behaviors and capabilities of WarpDrive's `Model` class,
+ * and because there is little distinction between Model and a ReactiveResource in LegacyMode we refer
+ * to both of these approaches as LegacyMode. This mode is the default experience in V5.
+ *
+ * In LegacyMode:
+ *
+ * - records are mutable
+ * - local changes immediately reflect app wide
+ * - records have all the APIs of Model (references, state props, currentState, methods etc)
+ * - the continued use of `@warp-drive-mirror/legacy` is required (though most imports from it can be removed)
+ * - `async: true` relationships are supported (but not recommended outside of [LinksMode](/guides/the-manual/misc/links-mode.md))
+ *
+ * ---
+ *
+ * **PolarisMode** is an upcoming suite of features that will become the default experience in V6.
+ *
+ * In PolarisMode:
+ *
+ * - records are immutable, unless creating a new resource or explicitly checking out a record for editing
+ * - local changes are isolated until committed, displaying only via the editable version of the record
+ * - records have a more limited API, focused on only what is in their schema.
+ * - some common operations may have more friction to perform because intended utilities are not yet available
+ * - `async: true` relationships are not supported (see [LinksMode](/guides/the-manual/misc/links-mode.md))
+ * - The `@warp-drive-mirror/legacy` package is not required
+ *
+ * These modes are interopable. The reactive object (record) for a resource in PolarisMode can relate to
+ * a record in LegacyMode and vice-versa. This interopability is true whether the record in LegacyMode is
+ * a ReactiveResource or a Model.
+ *
+ * ---
+ *
+ * ## Basic Usage
+ *
+ * ReactiveResource is a reactive object that transforms raw data from an associated
+ * cache into reactive data backed by Signals.
+ *
+ * The shape of the object and the transformation of raw cache data into its
+ * reactive form is controlled by a resource schema.
+ *
+ * For instance, lets say your API is a [{json:api}](https://jsonapi.org) and your store is using
+ * the Cache provided by {@link @warp-drive-mirror/json-api! | @warp-drive-mirror/json-api}, and a request
+ * returns the following raw data:
+ *
+ * ```ts
+ * {
+ *   data: {
+ *     type: 'user',
+ *     id: '1',
+ *     attributes: { firstName: 'Chris', lastName: 'Thoburn' },
+ *     relationships: { pets: { data: [{ type: 'dog', id: '1' }] }}
+ *   },
+ *   included: [
+ *     {
+ *       type: 'dog',
+ *       id: '1',
+ *       attributes: { name: 'Rey' },
+ *       relationships: { owner: { data: { type: 'user', id: '1' }}}
+ *     }
+ *   ]
+ * }
+ * ```
+ *
+ * We could describe the `'user'` and `'dog'` resources in the above payload
+ * with the following schemas:
+ *
+ * ```ts
+ * store.schema.registerResources([
+ *   {
+ *     type: 'user',
+ *     identity: { type: '@id', name: 'id' },
+ *     fields: [
+ *       {
+ *         type: '@identity',
+ *         name: '$type',
+ *         kind: 'derived',
+ *         options: { key: 'type' },
+ *       },
+ *       { kind: 'field', name: 'firstName' },
+ *       { kind: 'field', name: 'lastName' },
+ *       {
+ *         kind: 'derived',
+ *         name: 'name',
+ *         type: 'concat',
+ *         options: { fields: ['firstName', 'lastName'], separator: ' ' }
+ *       },
+ *       {
+ *         kind: 'hasMany',
+ *         name: 'pets',
+ *         type: 'pet',
+ *         options: {
+ *           async: false,
+ *           inverse: 'owner',
+ *           polymorphic: true,
+ *           linksMode: true,
+ *         }
+ *       }
+ *     ]
+ *   },
+ *   {
+ *     type: 'dog',
+ *     identity: { type: '@id', name: 'id' },
+ *     fields: [
+ *       {
+ *         type: '@identity',
+ *         name: '$type',
+ *         kind: 'derived',
+ *         options: { key: 'type' },
+ *       },
+ *       { kind: 'field', name: 'name' },
+ *       {
+ *         kind: 'belongsTo',
+ *         name: 'owner',
+ *         type: 'user',
+ *         options: {
+ *           async: false,
+ *           inverse: 'pets',
+ *           as: 'pet',
+ *           linksMode: true,
+ *         }
+ *       }
+ *     ]
+ *   }
+ * ]);
+ * ```
+ *
+ * With these schemas in place, the reactive objects that the store would
+ * provide us whenever we encountered a `'user'` or a `'dog'` would be:
+ *
+ * ```ts
+ * interface Pet {
+ *   readonly id: string;
+ *   readonly owner: User;
+ * }
+ *
+ * interface Dog extends Pet {
+ *   readonly $type: 'dog';
+ *   readonly name: string;
+ * }
+ *
+ * interface EditableUser {
+ *   readonly $type: 'user';
+ *   readonly id: string;
+ *   firstName: string;
+ *   lastName: string;
+ *   readonly name: string;
+ *   pets: Array<Dog | Pet>;
+ * }
+ *
+ * interface User {
+ *   readonly $type: 'user';
+ *   readonly id: string;
+ *   readonly firstName: string;
+ *   readonly lastName: string;
+ *   readonly name: string;
+ *   readonly pets: Readonly<Array<Dog | Pet>>;
+ *   [Checkout](): Promise<EditableUser>
+ * }>
+ * ```
+ *
+ * Note how based on the schema the reactive object we receive is able to produce
+ * `name` on user (despite no name field being in the cache), provide `$type`
+ * pulled from the identity of the resource, and flatten the individual attributes
+ * and relationships onto the record for easier use.
+ *
+ * Notice also how we typed this object with `readonly`. This is because while
+ * ReactiveResource instances are ***deeply reactive***, they are also ***immutable***.
+ *
+ * We can mutate a ReactiveResource only be explicitly asking permission to do so, and
+ * in the process gaining access to an editable copy. The immutable version will
+ * not show any in-process edits made to this editable copy.
+ *
+ * ```ts
+ * import { checkout } from '@warp-drive-mirror/core/reactive';
+ *
+ * const editable = await checkout<EditableUser>(user);
+ * ```
+ *
+ * ## Utilities
+ *
+ * ReactiveResource provides a schema builder that simplifies setting up a couple of
+ * conventional fields like identity and `$type`. We can rewrite the schema
+ * definition above using this utility like so:
+ *
+ * ```ts
+ * import { withDefaults } from '@warp-drive-mirror/core/reactive';
+ *
+ * store.schema.registerResources([
+ *   withDefaults({
+ *     type: 'user',
+ *     fields: [
+ *       { kind: 'field', name: 'firstName' },
+ *       { kind: 'field', name: 'lastName' },
+ *       {
+ *         kind: 'derived',
+ *         name: 'name',
+ *         type: 'concat',
+ *         options: { fields: ['firstName', 'lastName'], separator: ' ' }
+ *       },
+ *       {
+ *         kind: 'hasMany',
+ *         name: 'pets',
+ *         type: 'pet',
+ *         options: {
+ *           async: false,
+ *           inverse: 'owner',
+ *           polymorphic: true,
+ *           linksMode: true,
+ *           resetOnRemoteUpdate: false,
+ *         }
+ *       }
+ *     ]
+ *   }),
+ *   withDefaults({
+ *     type: 'dog',
+ *     fields: [
+ *       { kind: 'field', name: 'name' },
+ *       {
+ *         kind: 'belongsTo',
+ *         name: 'owner',
+ *         type: 'user',
+ *         options: {
+ *           async: false,
+ *           inverse: 'pets',
+ *           as: 'pet',
+ *           linksMode: true,
+ *           resetOnRemoteUpdate: false,
+ *         }
+ *       }
+ *     ]
+ *   })
+ * ]);
+ * ```
+ *
+ * ## Type Support
+ *
+ * ### Resource Schemas
+ *
+ * - {@link PolarisResourceSchema}
+ * - {@link LegacyResourceSchema}
+ * - {@link ObjectSchema}
+ *
+ * ### Resource Schema Type Utils
+ *
+ * - {@link resourceSchema}
+ * - {@link objectSchema}
+ * - {@link isResourceSchema}
+ * - {@link isLegacyResourceSchema}
+ *
+ * ### Field Schemas
+ *
+ * - {@link LegacyModeFieldSchema}
+ * - {@link PolarisModeFieldSchema}
+ *
+ * @summary Schema-driven reactive records, arrays, and documents the store builds from cached data, plus the
+ * `SchemaService` and schema types that define them.
+ * @module
+ */
+import { C as getRequestState, Cn as Transformation, D as ResolvedPromise, Dt as ReactiveDataDocument, E as RejectedPromise, En as withDefaults, H as checkout, K as LegacyManyArray, O as getPromiseState, Ot as ReactiveDocument, R as instantiateRecord, S as ResolvedRequest, Sn as SchemaService, T as PromiseState, Tn as registerDerivations, U as commit, V as ReactiveResource, _ as CancelledRequest, b as RequestLoadingState, bn as ExtensionDef, c as AutorefreshBehaviorCombos, dt as LegacyQueryArray, f as RecoveryFeatures, ft as LegacyLiveArray, g as createRequestSubscription, gt as Checkout, h as SubscriptionArgs, kt as ReactiveErrorDocument, l as AutorefreshBehaviorType, m as RequestSubscription, mt as ReactiveResourceArray, p as RequestArgs, u as ContentFeatures, v as PendingRequest, vn as CAUTION_MEGA_DANGER_ZONE_Extension, w as PendingPromise, wn as fromIdentity, x as RequestState, xn as ProcessedExtension, y as RejectedRequest, z as teardownRecord } from "./internal-BOC6nyCi.js";
 export { type AutorefreshBehaviorCombos, type AutorefreshBehaviorType, type CAUTION_MEGA_DANGER_ZONE_Extension, type CancelledRequest, Checkout, type ContentFeatures, type ExtensionDef, type LegacyLiveArray, type LegacyManyArray, type LegacyQueryArray, type PendingPromise, type PendingRequest, type ProcessedExtension, type PromiseState, type ReactiveDataDocument, type ReactiveDocument, type ReactiveErrorDocument, type ReactiveResource, type ReactiveResourceArray, type RecoveryFeatures, type RejectedPromise, type RejectedRequest, type RequestArgs, type RequestLoadingState, type RequestState, type RequestSubscription, type ResolvedPromise, type ResolvedRequest, SchemaService, type SubscriptionArgs, type Transformation, checkout, commit, createRequestSubscription, fromIdentity, getPromiseState, getRequestState, instantiateRecord, registerDerivations, teardownRecord, withDefaults };

package/dist/reactive.js

@@ -1,5 +1,5 @@
-import { d as getRequestState, t as getPromiseState, u as createRequestSubscription } from "./-private-BpyvBYFj.js";
+import { d as getRequestState, t as getPromiseState, u as createRequestSubscription } from "./-private-Y-13dsHO.js";
 import { t as Checkout } from "./-private-CmNOwhK0.js";
-import { a as fromIdentity, c as instantiateRecord, d as commit, i as SchemaService, l as teardownRecord, o as registerDerivations, s as withDefaults, u as checkout } from "./src-DlNeupkA.js";
+import { a as fromIdentity, c as instantiateRecord, d as commit, i as SchemaService, l as teardownRecord, o as registerDerivations, s as withDefaults, u as checkout } from "./src-DDLNZD8D.js";
 
 export { Checkout, SchemaService, checkout, commit, createRequestSubscription, fromIdentity, getPromiseState, getRequestState, instantiateRecord, registerDerivations, teardownRecord, withDefaults };

package/dist/{request-MiwUbGdT.js → request-DUGpwUhf.js}

@@ -732,17 +732,21 @@ function createFuture(owner) {
 /**
 * Brands the supplied object with the supplied response type.
 *
-* The [Typing Requests](/guides/the-manual/requests/typing-requests) guide shows how
-* to use it.
+* Call it inside a [builder](/guides/the-manual/requests/builders), so the type is part of
+* the builder's contract and every caller gets it through inference. Calling it inline
+* where the request is made is a cast. The [Typing Requests](/guides/the-manual/requests/typing-requests)
+* guide shows how to use it.
 *
 * ```ts
 * import type { ReactiveDataDocument } from '@warp-drive-mirror/core/reactive';
 * import { withResponseType } from '@warp-drive-mirror/core/request';
 * import type { User } from '#/data/user.ts'
 *
-* const result = await store.request(
-*  withResponseType<ReactiveDataDocument<User>>({ url: '/users/1' })
-* );
+* export function getUser(id: string) {
+*   return withResponseType<ReactiveDataDocument<User>>({ url: `/users/${id}` });
+* }
+*
+* const result = await store.request(getUser('1'));
 *
 * result.content.data; // will have type User
 * ```
@@ -758,16 +762,20 @@ function withResponseType(obj) {
 * wrapped in {@link ReactiveDataDocument}. This is a convenience for
 * the common case of using {@link withResponseType} with `ReactiveDataDocument`.
 *
-* The [Typing Requests](/guides/the-manual/requests/typing-requests#typing-reactive-responses)
+* Like `withResponseType`, call it inside a [builder](/guides/the-manual/requests/builders)
+* rather than where the request is made. The
+* [Typing Requests](/guides/the-manual/requests/typing-requests#typing-reactive-responses)
 * guide shows how to use it.
 *
 * ```ts
 * import { withReactiveResponse } from '@warp-drive-mirror/core/request';
 * import type { User } from '#/data/user.ts'
 *
-* const result = await store.request(
-*   withReactiveResponse<User>({ url: '/users/1' })
-* );
+* export function getUser(id: string) {
+*   return withReactiveResponse<User>({ url: `/users/${id}` });
+* }
+*
+* const result = await store.request(getUser('1'));
 *
 * result.content.data; // will have type User
 * ```
@@ -777,9 +785,11 @@ function withResponseType(obj) {
 * ```ts
 * type PageMeta = { page: { limit: number; offset: number }; total?: number };
 *
-* const result = await store.request(
-*   withReactiveResponse<User[], PageMeta>({ url: '/users' })
-* );
+* export function getUsers() {
+*   return withReactiveResponse<User[], PageMeta>({ url: '/users' });
+* }
+*
+* const result = await store.request(getUsers());
 *
 * result.content.meta?.total; // number | undefined
 * ```
@@ -800,4 +810,4 @@ const withBrand = withResponseType;
 
 //#endregion
 export { upgradePromise as a, executeNextHandler as c, getRequestResult as d, setPromiseResult as f, createDeferred as i, clearRequestResult as l, assertValidRequest as m, withReactiveResponse as n, DOMError as o, cloneResponseProperties as p, withResponseType as r, IS_CACHE_HANDLER as s, withBrand as t, getPromiseResult as u };
-//# sourceMappingURL=request-MiwUbGdT.js.map
+//# sourceMappingURL=request-DUGpwUhf.js.map