@withone/cli 1.20.3 → 1.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -98,7 +98,7 @@ one flow validate welcome-customer
98
98
  one flow execute welcome-customer -i email=jane@example.com
99
99
  ```
100
100
 
101
- Workflows are stored as JSON at `.one/flows/<key>.flow.json` and support conditions, loops, while loops, parallel steps, transforms, sub-flows, pagination, bash steps, and more. Run `one guide flows` for the full reference.
101
+ Workflows live under `.one/flows/<key>/flow.json` with an optional `lib/` subfolder for `.mjs` code modules — create new flows in this folder layout. (The legacy single-file layout `.one/flows/<key>.flow.json` is deprecated but still loads for backward compatibility.) Flows support conditions, loops, while loops, parallel steps, transforms, sub-flows, pagination, bash steps, and external `.mjs` code modules. Run `one guide flows` for the full reference.
102
102
 
103
103
  ## How it works
104
104
 
@@ -284,7 +284,7 @@ In agent mode (`--agent`), the JSON response includes the guide content and an `
284
284
 
285
285
  ### `one flow create [key]`
286
286
 
287
- Create a workflow from a JSON definition. Workflows are saved to `.one/flows/<key>.flow.json`.
287
+ Create a workflow from a JSON definition. New workflows are always saved to the folder layout at `.one/flows/<key>/flow.json` (with a `lib/` subfolder scaffolded for code modules). The legacy `.one/flows/<key>.flow.json` single-file layout is deprecated; existing legacy files continue to load and run unchanged for backward compatibility.
288
288
 
289
289
  ```bash
290
290
  # From a --definition flag
@@ -300,7 +300,7 @@ one flow create my-flow --definition '...' -o ./custom/path.json
300
300
  | Option | What it does |
301
301
  |--------|-------------|
302
302
  | `--definition <json>` | Workflow definition as a JSON string |
303
- | `-o, --output <path>` | Custom output path (default: `.one/flows/<key>.flow.json`) |
303
+ | `-o, --output <path>` | Custom output path (default: `.one/flows/<key>/flow.json`) |
304
304
 
305
305
  ### `one flow execute <key>`
306
306