@warp-drive-mirror/core 5.10.0-alpha.18 → 5.10.0-alpha.19

package/dist/build-config/babel-macros.d.ts

@@ -1,2 +1,7 @@
+/**
+ * @module
+ * @summary The `macros` function, which returns the Babel plugins that strip WarpDrive deprecation, canary-feature,
+ * debug-logging and env code at build time.
+ */
 import { macros } from "@warp-drive-mirror/build-config/babel-macros";
 export { macros };

package/dist/build-config/canary-features.d.ts

@@ -1 +1,6 @@
+/**
+ * @module
+ * @summary Build-time flags, such as `JSON_API_CACHE_VALIDATION_ERRORS`, that gate unreleased WarpDrive features for
+ * canary builds.
+ */
 export * from "@warp-drive-mirror/build-config/canary-features";

package/dist/build-config/debugging.d.ts

@@ -1 +1,60 @@
+/**
+ * # Log Instrumentation <Badge type="tip" text="debug only" />
+ *
+ * Many portions of the internals are helpfully instrumented with logging.
+ * This instrumentation is always removed from production builds.
+ *
+ * The [Debugging](/guides/the-manual/debugging/) guide explains what each flag logs.
+ *
+ * Log instrumentation is "regionalized" to specific concepts and concerns
+ * to enable you to enable/disable just the areas you are interested in.
+ *
+ * To activate a particular group of logs set the appropriate flag to `true`
+ * either in your build config or via the runtime helper.
+ *
+ *
+ * ## Runtime Activation
+ *
+ * ::: tip 💡 Just Works in browser Dev Tools!
+ * No import is needed, and the logging config is preserved when the page is refreshed
+ * :::
+ *
+ * ```ts
+ * setWarpDriveLogging({
+ *   LOG_CACHE: true,
+ *   LOG_REQUESTS: true,
+ * })
+ * ```
+ *
+ * A runtime helper is attached to `globalThis` to enable activation of the logs
+ * from anywhere in your application including from the devtools panel.
+ *
+ * The runtime helper overrides any build config settings for the given flag
+ * for the current browser tab. It stores the configuration you give it in
+ * `sessionStorage` so that it persists across page reloads of the current tab,
+ * but not across browser tabs or windows.
+ *
+ * If you need to deactivate the logging, you can call the helper again with the
+ * same flag set to `false` or just open a new tab/window.
+ *
+ * ## Buildtime Activation
+ *
+ * ```ts
+ * setConfig(__dirname, app, {
+ *   debug: {
+ *     LOG_CACHE: true,
+ *     LOG_REQUESTS: false,
+ *     LOG_NOTIFICATIONS: true,
+ *   }
+ * });
+ * ```
+ *
+ * The build config settings are used to set the default values for the
+ * logging flags. Any logging flag that is not set in the build config
+ * will default to `false`.
+ *
+ * @summary Debug-only logging flags, such as `LOG_CACHE` and `LOG_REQUESTS`, set in build config or at runtime
+ * via `setWarpDriveLogging`.
+ * @module
+ */
 export * from "@warp-drive-mirror/build-config/debugging";

package/dist/build-config/deprecations.d.ts

@@ -1 +1,6 @@
+/**
+ * @module
+ * @summary Deprecation flags, such as `DEPRECATE_NON_STRICT_TYPES`, that keep deprecated WarpDrive behavior active
+ * until the build config drops it by `compatWith` version or by flag.
+ */
 export * from "@warp-drive-mirror/build-config/deprecations";

package/dist/build-config.d.ts

@@ -1,2 +1,19 @@
+/**
+ * This module provides a build-plugin that enables configuration of deprecations,
+ * optional features, development/testing support and debug logging.
+ *
+ * Available settings include:
+ *
+ * - {@link LOGGING | debugging}
+ * - {@link DEPRECATIONS | deprecations}
+ * - {@link FEATURES | features}
+ * - {@link WarpDriveConfig.polyfillUUID | polyfillUUID}
+ * - {@link WarpDriveConfig.includeDataAdapterInProduction | includeDataAdapterInProduction}
+ * - {@link WarpDriveConfig.compatWith | compatWith}
+ *
+ * @summary Build-time configuration for WarpDrive: `setConfig` and its babel plugin for deprecations, features,
+ * debug logging, and polyfill settings.
+ * @module
+ */
 import { WarpDriveConfig, babelPlugin, setConfig } from "@warp-drive-mirror/build-config";
 export { type WarpDriveConfig, babelPlugin, setConfig };

package/dist/configure.d.ts

@@ -1,2 +1,10 @@
+/**
+ * Provides a configuration API for the reactivity system
+ * that WarpDrive should use.
+ *
+ * @summary Provides `setupSignals`, which tells WarpDrive which signal and reactivity library to build its
+ * reactive values on.
+ * @module
+ */
 import { a as registerSignals, n as HooksOptions, o as setupSignals, r as SignalHooks } from "./configure-CodrrdQr.js";
 export { type HooksOptions, type SignalHooks, registerSignals, setupSignals };

package/dist/graph/-private.js

@@ -391,7 +391,7 @@ function upgradeDefinition(graph, key, propertyName, isImplicit = false) {
 		})(storeWrapper.schema.hasResource({ type: inverseType }));
 		inverseDefinition = null;
 	} else {
-		inverseKey = inverseForRelationship(getStore(storeWrapper), key, propertyName);
+		inverseKey = inverseForRelationship(getStore(storeWrapper), key, meta.name);
 		if (!inverseKey && definition.isPolymorphic && definition.inverseKey) inverseDefinition = {
 			kind: "belongsTo",
 			key: definition.inverseKey,
@@ -416,6 +416,7 @@ function upgradeDefinition(graph, key, propertyName, isImplicit = false) {
 				if (!test) throw new Error(`Expected ${inverseKey} to be a relationship`);
 			})(isRelationshipField(metaFromInverse));
 			inverseDefinition = upgradeMeta(metaFromInverse);
+			inverseKey = inverseDefinition.key;
 		}
 	}
 	if (!inverseDefinition) {