Repository navigation
DYNAMO UI fixes and flow settings with explained choices - #482
Merged
Merged
Conversation
…et and recommended models The wizard shows models that take the uploaded variable first, close matches as a second tier, and prefills the question, period and region (editable).
…s collapsed Boundary options show region names (never ids), sorted and grouped by category, in a type-to-filter combobox. Numbered parts of one registered region (TRINITY_1..55) collapse into one family entry that selects the whole region and expands to single parts. The map shows one category at a time and draws the selection highlighted over faint context. Layer configs gain label_field, label_prefix and label_suffix so the GMA layer reads 'GMA 1' instead of '1'.
…tcome producers first The picker led each option with its description and listed the same variable under its catalog id and its adapter URI. Options now lead with the humanized label, show the description as secondary text, and drop repeats by id and, across merged sources, by label. The Models step only filtered, in tree order, and matched a flow's output by id alone. Rows that declare the outcome (by id or name) now sort first, then rows reachable by a transform, each with a reason; a search keeps an exact match the semantic index does not carry.
Text similarity alone put a flow's output variable (narrative frames) above the corpus variable for a transcript upload. Suggestions now rank first the variables a registered flow or model input accepts these files under, then those an input takes without a declared format, then format mismatches, then variables nothing takes, keeping the semantic order within each group. Each suggestion says which flows and models take it.
Add modelcatalog_configuration_flow.settings_json (visibility and fixed per
setting) and expose it to the same roles as thread_bindings_json. The adapter
passes a piece's setting description (title, choices, bounds, advanced) through
its piece summary and plan parameters, resolves each setting for a runner
(GET /flows/{id}/settings), checks hidden and fixed settings have a value, and
refuses a runner's value for a fixed or hidden setting at submit. The catalog
API writes the settings and mirrors defaults, fixed values, choices and bounds
onto the flow's parameter rows, and relays the settings read.
…x, hide or default them Add a shared setting input (dropdown with the chosen choice's explanation, bounded number box, checkbox, text). Each setting in a step card now shows the piece's title and explanation and lets the author choose a default or a fixed value and whether it is shown, advanced or hidden. The choices are saved as the flow's settings and sent to the check.
…el multi-select
A flow's settings show the piece's title and explanation, with a dropdown for
choices, a bounded number box and a checkbox, filled with the flow's default.
Advanced settings sit in a collapsed section, hidden ones are not shown, and
fixed ones are listed read-only. A value left at the default is not bound, so the
author's defaults are still accepted at run. A model parameter with accepted values
is a multi-select, and several values are several runs. Settings are read through
the catalog API's new GET /flows/{id}/settings, falling back to the parameter rows.
…s, conflicts Compare refused runner values trimmed, without case and through aliases. The flow check now refuses values for credential-like setting names, a thread-filled setting that is also fixed or hidden, and pieces that describe a shared setting two ways; the hidden message names the setting and step. A model multi-select keeps values that are not accepted, flagged. The builder says hidden is not secret. Tests and docs updated.
…feat/dynamo-ui-and-flow-settings
… into feat/dynamo-ui-and-flow-settings
…' into feat/dynamo-ui-and-flow-settings # Conflicts: # ui-react/src/pages/datasets/DatasetUploadPage.tsx
…anking' into feat/dynamo-ui-and-flow-settings
…t/dynamo-ui-and-flow-settings
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Nov 20, 2026
This was referenced Nov 20, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Combines #477, #478, #479, #480 and #481 into one PR so they build and deploy together. Each part's details are in its original PR.
Parts
docs/design/2026-11-20-flow-setting-schemas.md): settings render from each piece's JSON Schema like Tapisapp.jsonarguments (titles, explained dropdowns, bounded numbers, defaults, advanced folded, hidden omitted, fixed read-only); flow authors set default/fixed and shown/advanced/hidden; newmodelcatalog_configuration_flow.settings_json(migration1771300000047); adapterGET /flows/{id}/settingsand server-side refusal of runner values on fixed/hidden settings; model parameters with accepted values become a multi-select. QA and security reviewed, findings fixed.Combined checks (this branch)
tsc -band prettier clean.test_demo_apifailures (git-ignored.env).tsc --noEmitclean.DatasetUploadPage.tsx), resolved by keeping both sides.Rollout
Apply the Hasura migration and metadata before the new code. After deploy: rerun the adapter
/admin/sync-from-mint; register the library's new piece revisions (wmobley/Semantic-Sensemakingfeat/setting-schemas) and re-register the Sensemaking flows' settings.Do not merge until dev testing is scheduled.
🤖 Generated with Claude Code