mammoth-cli 2.0.47__tar.gz → 2.0.48__tar.gz

{mammoth_cli-2.0.47 → mammoth_cli-2.0.48}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.47
+Version: 2.0.48
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk

{mammoth_cli-2.0.47 → mammoth_cli-2.0.48}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.0.47"
+__version__ = "2.0.48"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.47 → mammoth_cli-2.0.48}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.47
+version: 2.0.48
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines (join, merge, pivot, filter, clean), dashboards, exports, and handoffs."
 ---
 
@@ -70,7 +70,7 @@ mammoth view transform --help              # every data transformation
 | Goal | Command |
 |---|---|
 | Combine two datasets on a key (merge, VLOOKUP) | `view transform join`; one value per key: `view transform lookup` |
-| Add rows to an existing dataset | `file upload FILE --input '{"append_to_ds_id": DATASET_ID}'` |
+| Add rows to an existing dataset, or combine two sources | `file upload FILE --input '{"append_to_ds_id": DATASET_ID}'`; then `discard-duplicates` and diff `row_count` before/after ([about Mammoth](references/about-mammoth.md#view-settings-and-what-has-no-command)) |
 | Keep or remove rows | `view transform filter` |
 | Remove duplicate rows | `view transform discard-duplicates` |
 | Totals, counts, averages per group | `view transform pivot` |

{mammoth_cli-2.0.47 → mammoth_cli-2.0.48}/mammoth_cli/bundled_skill/mammoth-cli/references/about-mammoth.md

@@ -140,7 +140,12 @@ No command:
 - **Union or append two views.** There is no union task. Upload a file into
   an existing dataset with `append_to_ds_id`, or send a view's rows into an
   existing dataset with `view export dataset` (`target_ds_id` and
-  `save_as_mode` `APPEND_TO_DS`; that mode is untried on release).
+  `save_as_mode` `APPEND_TO_DS`; that mode is untried on release). A row
+  present in both sources lands twice: note the appended view's `row_count`
+  (`view get`), run `view transform discard-duplicates` on it (`ignore_columns`
+  for any column you added per source, e.g. a region tag, since it would
+  make shared rows differ), read `row_count` again, and report the
+  difference as duplicates removed.
 - **Hide or reorder columns.** Display changes in the web app; they do not
   change the data.
 

{mammoth_cli-2.0.47 → mammoth_cli-2.0.48}/mammoth_cli/commands/view.py

@@ -805,7 +805,9 @@ def _trim_rows(data: Any, limit: Any) -> Any:
         return data
     try:
         cap = int(limit)
-    except (TypeError, ValueError):
+    except TypeError:
+        cap = _DATA_GET_DEFAULT_LIMIT
+    except ValueError:
         cap = _DATA_GET_DEFAULT_LIMIT
     rows = data[_ROWS_KEY]
     total = len(rows)
@@ -2040,12 +2042,16 @@ def view_export_specialized(invocation: Invocation) -> HandlerResult:
         )
     for field in required:
         _require_field(document, field)
-    # Every typed destination is an external effect except internal dataset
-    # creation, which is still a mutation. Requiring --yes keeps all helpers
-    # promptless and makes the side effect explicit for agents.
+    # The manifest is the single source of truth for each destination's
+    # confirmation policy (dataset export has no external effect and needs
+    # none; every other destination is external_effect/yes_always). Deriving
+    # it here, rather than hardcoding one policy for every route, keeps the
+    # in-app agent's confirmation card (which reads the manifest) in sync
+    # with what the CLI actually enforces.
+    export_record = command_by_id(invocation.command_id) or {}
     enforce_confirmation(
         invocation,
-        policy=POLICY_YES_ALWAYS,
+        policy=str(export_record.get("confirmation") or POLICY_YES_ALWAYS),
         action=f"export view {dataview_id} via {invocation.command_id.rsplit('.', 1)[-1]}",
     )
     kwargs = dict(document)
@@ -2062,8 +2068,10 @@ def view_export_specialized(invocation: Invocation) -> HandlerResult:
             "dataset_id": data,
             "project_id": int(target_project) if target_project is not None else project_id,
             "source_view_id": dataview_id,
-            "next": f"mammoth view list {data}"
-            + (f" --project {int(target_project)}" if target_project is not None else ""),
+            "next": (
+                f"mammoth view list {data}"
+                + (f" --project {int(target_project)}" if target_project is not None else "")
+            ),
         }
     return data, _meta(invocation, auth.workspace_id, project_id)
 

{mammoth_cli-2.0.47 → mammoth_cli-2.0.48}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mammoth-cli"
-version = "2.0.47"
+version = "2.0.48"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"