@danceroutine/tango-schema 1.1.3 → 1.2.0

package/dist/model/relations/ResolvedRelationGraphBuilder.d.ts

@@ -0,0 +1,48 @@
+import type { Model } from '../../domain/index';
+import type { FinalizedStorageArtifacts } from '../fields/FinalizedStorageArtifacts';
+import type { NormalizedRelationStorageDescriptor } from './NormalizedRelationStorageDescriptor';
+import type { ResolvedRelationGraph } from './ResolvedRelationGraph';
+type GraphBuilderOptions = {
+    version: number;
+    models: readonly Model[];
+    storage: FinalizedStorageArtifacts;
+    resolveRef: (ref: NormalizedRelationStorageDescriptor['targetRef']) => Model;
+};
+/**
+ * Resolution-stage builder that turns normalized relation descriptors into the
+ * registry-scoped resolved relation graph.
+ *
+ * This is the final pipeline stage in the relations subdomain. It combines:
+ *
+ * - normalized field-authored relation descriptors
+ * - explicit model-level relation names from `RelationBuilder`
+ * - finalized storage artifacts from the registry
+ *
+ * The result is the canonical named relation graph used by ORM-facing
+ * consumers.
+ */
+export declare class ResolvedRelationGraphBuilder {
+    private readonly options;
+    private readonly byModel;
+    private readonly byEdgeId;
+    private readonly matchedOverrides;
+    constructor(options: GraphBuilderOptions);
+    static build(options: GraphBuilderOptions): ResolvedRelationGraph;
+    /**
+     * Resolve every model's normalized relation descriptors into a single
+     * registry-scoped graph and fail when authoring ambiguity remains.
+     */
+    build(): ResolvedRelationGraph;
+    private addModelRelations;
+    private addReferenceRelations;
+    private findForwardOverride;
+    private findReverseOverride;
+    private assertAllOverridesMatched;
+    private addResolvedRelation;
+    private getPrimaryKey;
+    private markOverrideMatched;
+    private buildOverrideMarker;
+    private resolveRelationTargetKey;
+    private deriveReverseName;
+}
+export {};

package/dist/model/relations/SchemaNaming.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Shared naming policy for the model and relations subdomains.
+ *
+ * These helpers are not an authoring or graph stage on their own. They are the
+ * cross-cutting policy layer used by both model construction and relation
+ * resolution when Tango derives table names, aliases, and synthesized relation
+ * names in a Django-style shape.
+ */
+export declare function toSnakeCase(value: string): string;
+export declare function pluralize(value: string): string;
+export declare function deriveTableName(name: string): string;

package/dist/model/relations/index.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Domain boundary barrel for relation authoring.
+ *
+ * The relations subdomain has three internal layers:
+ *
+ * - authoring: `RelationBuilder`
+ * - normalization: field-authored relations become normalized descriptors
+ * - resolution: normalized descriptors become the registry-scoped relation graph
+ *
+ * Only the authoring surface is exported here. The later pipeline stages stay
+ * internal until Tango intentionally publishes them as supported contracts.
+ */
+export { RelationBuilder } from './RelationBuilder';