flowbase-cli 0.1.19__tar.gz → 0.1.20__tar.gz

{flowbase_cli-0.1.19/src/flowbase_cli.egg-info → flowbase_cli-0.1.20}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: flowbase-cli
-Version: 0.1.19
+Version: 0.1.20
 Summary: Command line client for the FlowBase OpenAPI
 Author: DeepFlowAI
 License: Apache-2.0
@@ -356,6 +356,8 @@ Matching uses saved current-record values. Empty matching inputs return `pending
 
 `flowbase docs catalogs page-value-rules` describes authoring and the edit sequence. Page snapshots support `setFieldValue` and `setDefaultFieldValue`; sources can traverse up to five single-record relations. `pages evaluate` continues to preview field states and component visibility only.
 
+Create and detail Page actions accept an optional explicit `conversion`: `mapOptions` with `mappings: [{sourceOptionId, targetOptionId}]`, `copyOptions` for the same multiple-select definition through a relation, `truncateDate` for lower date precision, or `extractDate` for datetime → date in Asia/Shanghai. Read the catalog for the complete contract. Mappings use stable identities, never option names. Partial mappings warn; an unmapped runtime value fails the entire action. Disabled rules may retain inactive targets but must retain valid identities. Ordinary record writes remain strict and do not implicitly execute these conversions.
+
 ```bash
 flowbase records get OBJECT RECORD
 flowbase records page-value-context OBJECT RECORD

flowbase_cli-0.1.19/PKG-INFO → flowbase_cli-0.1.20/README.md

@@ -1,12 +1,3 @@
-Metadata-Version: 2.4
-Name: flowbase-cli
-Version: 0.1.19
-Summary: Command line client for the FlowBase OpenAPI
-Author: DeepFlowAI
-License: Apache-2.0
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-
 # FlowBase CLI
 
 `flowbase` is the official command line client for the FlowBase OpenAPI. It manages apps, objects, fields, views, custom pages, workflows, approval flows, dashboards, business records, roles, and configuration versions across the three FlowBase environments.
@@ -356,6 +347,8 @@ Matching uses saved current-record values. Empty matching inputs return `pending
 
 `flowbase docs catalogs page-value-rules` describes authoring and the edit sequence. Page snapshots support `setFieldValue` and `setDefaultFieldValue`; sources can traverse up to five single-record relations. `pages evaluate` continues to preview field states and component visibility only.
 
+Create and detail Page actions accept an optional explicit `conversion`: `mapOptions` with `mappings: [{sourceOptionId, targetOptionId}]`, `copyOptions` for the same multiple-select definition through a relation, `truncateDate` for lower date precision, or `extractDate` for datetime → date in Asia/Shanghai. Read the catalog for the complete contract. Mappings use stable identities, never option names. Partial mappings warn; an unmapped runtime value fails the entire action. Disabled rules may retain inactive targets but must retain valid identities. Ordinary record writes remain strict and do not implicitly execute these conversions.
+
 ```bash
 flowbase records get OBJECT RECORD
 flowbase records page-value-context OBJECT RECORD

{flowbase_cli-0.1.19 → flowbase_cli-0.1.20}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "flowbase-cli"
-version = "0.1.19"
+version = "0.1.20"
 description = "Command line client for the FlowBase OpenAPI"
 readme = "README.md"
 requires-python = ">=3.11"

{flowbase_cli-0.1.19 → flowbase_cli-0.1.20}/src/flowbase_cli/__init__.py

@@ -1,3 +1,3 @@
 """FlowBase OpenAPI CLI."""
 
-__version__ = "0.1.19"
+__version__ = "0.1.20"

{flowbase_cli-0.1.19 → flowbase_cli-0.1.20}/src/flowbase_cli/endpoints.py

@@ -1393,8 +1393,8 @@ PAGE_RULES = {
         "lookup.department": ("eq", "neq", "in", "not_in", "is_empty", "is_not_empty"),
     },
     "actions": (
-        {"type": "setDefaultFieldValue", "pageTypes": ("detail",), "requiredKeys": ("type", "fieldId", "sourceFieldId", "sourcePath"), "maxSourceHops": 5},
-        {"type": "setFieldValue", "pageTypes": ("detail",), "requiredKeys": ("type", "fieldId", "sourceFieldId", "sourcePath"), "maxSourceHops": 5},
+        {"type": "setDefaultFieldValue", "pageTypes": ("create", "detail"), "requiredKeys": ("type", "fieldId", "sourceFieldId", "sourcePath"), "optionalKeys": ("conversion",), "maxSourceHops": 5},
+        {"type": "setFieldValue", "pageTypes": ("create", "detail"), "requiredKeys": ("type", "fieldId", "sourceFieldId", "sourcePath"), "optionalKeys": ("conversion",), "maxSourceHops": 5},
         {
             "type": "setFieldState",
             "pageTypes": ("create", "detail"),
@@ -1635,8 +1635,15 @@ CATALOGS = {
         "bodyNaming": "Store bodies use snake_case (app_id, package_id, request_id, preview_confirmed), exactly as docs example shows.",
     },
     "page-value-rules": {
-        "authoring": "pages get/update preserves the full Page snapshot and baseRevision. Detail Pages support setFieldValue and setDefaultFieldValue; targets must be placed writable ordinary fields. sourcePath is empty for the current object or up to 5 single-relation hops. Enabled assignment chains are rejected.",
+        "authoring": "pages get/update preserves the full Page snapshot and baseRevision. Create and detail Pages support setFieldValue and setDefaultFieldValue; targets must be placed writable ordinary fields. sourcePath is empty for the current object or up to 5 single-relation hops. Enabled assignment chains are rejected. Create sources must be available before the record is saved.",
         "action": {"type": "setDefaultFieldValue", "fieldId": "fld_target", "sourceFieldId": "fld_source", "sourcePath": [{"relationFieldId": "fld_relation", "targetObjectId": "obj_source"}]},
+        "conversions": {
+            "mapOptions": {"type": "mapOptions", "mappings": [{"sourceOptionId": "opt_source", "targetOptionId": "opt_target"}]},
+            "copyOptions": {"type": "copyOptions"},
+            "truncateDate": {"type": "truncateDate"},
+            "extractDate": {"type": "extractDate"},
+            "rules": "Put an explicit conversion on the action. mapOptions supports ordinary single-to-single or multiple-to-multiple across field definitions, with at least one identity-owned mapping; partial mappings warn and fail at runtime when hit. Historical inactive sources are allowed; active rules cannot target inactive options. Disabled rules relax only target lifecycle. copyOptions supports the same multiple-select definition through a relation, never self-assignment. truncateDate only lowers day/month precision; extractDate converts datetime to Asia/Shanghai then extracts the target date precision. No implicit mapping, guessed names, text parsing or date padding. Missing conversion retains legacy semantics. Multiselect results deduplicate before maxSelections; one failure rejects the whole action.",
+        },
         "steps": ["records get OBJECT RECORD reads saved values; records page-value-context OBJECT RECORD [--page-id PAGE] returns the effective pageId/revision/updatedAt. Production uses published configuration; test Hosts use their effective configuration.", "records page-value-event OBJECT RECORD --json-file event.json: copy pageId/revision; values is the full current edit delta keyed by field key, changedFieldIds contains IDs changed by this event, previousSources carries the last response sources.", "Inspect errors before applying response values to the edit delta. Empty-only defaults skip nonempty targets; assignments run on relevant source/condition changes, not automatically on read or save. Formula collections use saved data.", "Save the merged edit delta using records update with pageId, valueRuleRevision=revision and updatedAt from context. The server rechecks page/field constraints without rerunning assignments. For whole-record bundles use bundle-save and its configVersion."],
         "updateExample": {"values": {"source": "edited", "target": "assigned"}, "pageId": "pag_xxx", "valueRuleRevision": "from-context", "updatedAt": "from-context"},
         "permissions": "Context/event require records:read and records:write, retain static field visibility/writability and approval locks, and never persist values. Old records update calls without Page context retain their existing behavior.",

{flowbase_cli-0.1.19 → flowbase_cli-0.1.20}/src/flowbase_cli/main.py

@@ -927,6 +927,9 @@ def _print_direct_release_preflight(preflight: dict[str, Any]) -> None:
         if isinstance(check, dict):
             mark = "OK" if check.get("ok") else "FAIL"
             print(f"  [{mark}] {check.get('label', '')}", file=sys.stderr)
+    for warning in preflight.get("warnings", []):
+        if isinstance(warning, dict):
+            print(f"  [WARN] {warning.get('message', '')}", file=sys.stderr)
     print(f"  RISK: {preflight.get('risk', 'This bypasses test environments.')}", file=sys.stderr)
 
 

flowbase_cli-0.1.19/README.md → flowbase_cli-0.1.20/src/flowbase_cli.egg-info/PKG-INFO

@@ -1,3 +1,12 @@
+Metadata-Version: 2.4
+Name: flowbase-cli
+Version: 0.1.20
+Summary: Command line client for the FlowBase OpenAPI
+Author: DeepFlowAI
+License: Apache-2.0
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
 # FlowBase CLI
 
 `flowbase` is the official command line client for the FlowBase OpenAPI. It manages apps, objects, fields, views, custom pages, workflows, approval flows, dashboards, business records, roles, and configuration versions across the three FlowBase environments.
@@ -347,6 +356,8 @@ Matching uses saved current-record values. Empty matching inputs return `pending
 
 `flowbase docs catalogs page-value-rules` describes authoring and the edit sequence. Page snapshots support `setFieldValue` and `setDefaultFieldValue`; sources can traverse up to five single-record relations. `pages evaluate` continues to preview field states and component visibility only.
 
+Create and detail Page actions accept an optional explicit `conversion`: `mapOptions` with `mappings: [{sourceOptionId, targetOptionId}]`, `copyOptions` for the same multiple-select definition through a relation, `truncateDate` for lower date precision, or `extractDate` for datetime → date in Asia/Shanghai. Read the catalog for the complete contract. Mappings use stable identities, never option names. Partial mappings warn; an unmapped runtime value fails the entire action. Disabled rules may retain inactive targets but must retain valid identities. Ordinary record writes remain strict and do not implicitly execute these conversions.
+
 ```bash
 flowbase records get OBJECT RECORD
 flowbase records page-value-context OBJECT RECORD