Repository navigation
Releases: STAPLE-verse/form-studio
Releases · STAPLE-verse/form-studio
Release list
v1.1.0
New builder features, all backward compatible.
New
- Undo and redo (buttons plus Ctrl/Cmd+Z), covering the builder, JSON editor and extension edits
- Expand all / Collapse all buttons
- Duplicate button on items
- Import answer options from a CSV or text file (Dropdown, Radio, Checkboxes), with a Remove all options button
- Copy items from another form: new optional
mods.itemSourcelets the host app supply the user's forms; the option only appears when it is provided (see STAPLE and MARKER) - Clearer help text under Field Type, and plain-language Format names (Email address, Web link (URL), ...)
Fixed
- Answer choices are kept when switching between Radio, Dropdown and Checkboxes
- A card or section no longer collapses when its variable name is changed
- The Create New popover opens above the plus icon instead of below
- A blank variable name can no longer be saved (it left an empty entry in the UI order)
v1.0.0 — First stable release
First stable release of form-studio, off pre-releases.
Since v0.2.0-rc.4
- Fixed the "Additional Settings" field editor rendering inside the
drag-and-drop tree, where an ancestortransformcould trap it in a
local stacking context and let unrelated page elements render above
it — it's now portaled todocument.body. - Fixed tooltip/info icons using a
z-indexthat could tie with (and
lose to) a host page's own sticky chrome — lowered to stay safely
under it. - Fixed the Monaco JSON editor panes showing a mismatched background
strip above/below the editor, and columns not staying the same
height as each other when one showed a parse error. - Corrected the Visual Builder's compatibility diagnostics: dropped
the internal[FS_*]error code from the user-facing message, and
fixed semantic binding being hidden on any read-only field instead
of only ones that need a legacy-schema migration first. - Bumped
@staple-verse/marker-template-runtimeto the stable
v1.0.0release (no contract changes from rc.4).
No breaking API changes from v0.2.0-rc.4.