No description
- Rust 47.8%
- JavaScript 22.6%
- Shell 14.8%
- CSS 7.8%
- HTML 5.9%
- Other 1.1%
7453ebd453
When the user picks an action through the modal (or binds by name),
the node's input_schema is now seeded from the action's declared
input_schema — if the node doesn't already have one. This is the
first half of the mapping story: for the common identity-case
(node input foo = action input foo), no further configuration is
needed. Users who actually need renames, literals, or passthroughs
will get explicit mapping rows in a follow-up (see hero_logic#3).
Flow:
1. User opens the picker, types to filter, clicks an action.
2. workflow_editor.js stores `p.action_name` / `p.action_context`.
3. `hlFetchAction(name)` fires; the cache entry already carries the
action's `input_schema` (populated by setupActionFetch).
4. When the fetch resolves, if the node's input_schema is absent /
empty / "{}", we copy the action's over and bumpRefresh to re-
render the card with the inherited fields.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| crates | ||
| src/logic | ||
| .gitignore | ||
| buildenv.sh | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Makefile | ||