@antelopejs/interface-dms-builder 0.3.0 → 0.3.1

package/dist/mapping.d.ts

@@ -52,6 +52,7 @@ export interface MapResourcesInput {
     connection: string;
     resources: MappedResource[];
     excluded?: ExcludedRelation[];
+    approvedPageRemovals?: PageRef[];
 }
 export interface LeftOutColumn {
     relation: string;
@@ -69,4 +70,8 @@ export interface MapResourcesResult {
     leftOut: LeftOutColumn[];
     category?: CategoryRef;
 }
+export interface MapResourcesPreview {
+    pagesToRemove: PageRef[];
+}
 export declare const MapResources: (input: MapResourcesInput) => Promise<OpResult<MapResourcesResult>>;
+export declare const PreviewMapResources: (input: MapResourcesInput) => Promise<OpResult<MapResourcesPreview>>;

package/dist/mapping.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.MapResources = void 0;
+exports.PreviewMapResources = exports.MapResources = void 0;
 const interface_core_1 = require("@antelopejs/interface-core");
 exports.MapResources = (0, interface_core_1.InterfaceFunction)();
+exports.PreviewMapResources = (0, interface_core_1.InterfaceFunction)();
 //# sourceMappingURL=mapping.js.map

package/dist/mapping.js.map

@@ -1 +1 @@
-{"version":3,"file":"mapping.js","sourceRoot":"","sources":["../src/mapping.ts"],"names":[],"mappings":";;;AAAA,+DAA+D;AAgMlD,QAAA,YAAY,GACvB,IAAA,kCAAiB,GAEd,CAAC"}
+{"version":3,"file":"mapping.js","sourceRoot":"","sources":["../src/mapping.ts"],"names":[],"mappings":";;;AAAA,+DAA+D;AAiNlD,QAAA,YAAY,GACvB,IAAA,kCAAiB,GAEd,CAAC;AAOO,QAAA,mBAAmB,GAC9B,IAAA,kCAAiB,GAEd,CAAC"}

package/docs/11.external-databases.md

@@ -186,6 +186,7 @@ const result = await MapResources({
 - **Where a proposal comes from.** `MapResources` reads the profile of a new relation through the catalog connection at map time, since D1 needs it. When the profile cannot be read, it takes the proposal from the connection's last `AnalyseDatabase`; when there is none either, D2 still applies by the column's name, no column becomes a badge, and the result warns `display_not_proposed`. A display that does not suit the column's declaration, such as a badge on a column declared `number`, is dropped when it was kept or proposed, and refused only when sent.
 - **A TableView's `tabs`**: `tabs: { column }` writes "All" and a tab per value of that column's badge to the TableView, over the `tabs` it holds; the column must be filterable and drawn as a badge. Left out, a page already mapped keeps its tabs, and a new relation takes the tabs T1 proposes among its filterable badge columns: a column left unfilterable is not tabbed. `null` writes none: it adds no tabs to a new relation, and removes from a page already mapped the tabs a mapping wrote from a badge, as `display: null` removes the badge. Tabs edited by hand are kept.
 - **Mapping again** a relation already mapped rewrites it from the new choices. Its page is created, kept or removed as `tableView` says, and takes the new `title`. The module's relation columns pointing at it take its new `label`.
+- **Before a remap that removes a page**, `PreviewMapResources(input)` answers `pagesToRemove` for the same input and writes nothing, so a caller can ask a person first. It refuses what `MapResources` refuses.
 - **The module's `package.json`** records the connection and the `excluded` tables with their reasons, so the next analysis does not propose those tables. Mapping one later removes it from the record:
 
   ```json

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antelopejs/interface-dms-builder",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "AntelopeJS interface for the DMS builder: create and edit pages, blocks, resources and queries in a DMS project from another module.",
   "keywords": [
     "antelopejs",