tosijs-ui 1.16.13 → 1.16.14

package/CHANGELOG.md

@@ -1,5 +1,48 @@
 # Changelog
 
+## 1.16.14
+
+More reach for curated schema forms (#221): into arrays and unions, grouped into sections,
+and usable as a review screen. All of it is off until you ask for it.
+
+- **A curation can reach inside arrays and unions.** Give an array's, a union's or an
+  object's entry its own `fields`, with paths relative to the property: for an array they
+  apply to every item (`thresholds: { fields: { value: 'Threshold' } }`), for a union to the
+  branch the value currently matches. Items and branches keep what is not shown, an error in
+  an item property that is not shown is listed by its real path, and a union's
+  `picker: false` hides the variant picker. One `fields` covers every branch of a union: a
+  path the active branch lacks is left out, a path no branch has says so.
+- **Sections.** An entry `{ section: 'Advanced', fields: {...}, collapsed?: true }` groups
+  fields in a titled panel. `collapsed: true` also works on an object or array entry. A
+  section or collapsed entry is marked `-invalid`, with a red title, while a field inside it
+  is in error. **TypeScript:** `FieldCuration`'s values now include `CuratedSection`, so code
+  that walks a curation and reads `entry.caption` needs the new guard: `isSection` is exported.
+- **Proposals, for review screens.** `form.proposals = { path: { value, reason?, source? } }`
+  shows each proposed value under its field with Accept and Reject. `value` stays the
+  current value until one is accepted; accepting fires `proposalaccept` then `change`,
+  rejecting fires `proposalreject`. `acceptProposal(path)` / `rejectProposal(path)` do it
+  from code, and `proposalView` renders a proposal your own way. A proposal can be for a
+  whole array, object or union, and an object item of an array can be proposed whole
+  (`list.0`). One for an array item follows its item when items move. `proposalView` is
+  given `ProposalContext.readOnly`, and its `accept` / `reject` do nothing while the form is
+  read-only. Works with or without a curation. New localized strings: `Proposed`, `Accept`, `Reject`,
+  `Proposed changes to fields not shown here`.
+- For TypeScript: `isSection` is exported; `ProposalContext.readOnly` tells a custom
+  `proposalView` that the form is read-only.
+- **Fixed: an array item with several fields laid them out in two columns**, so the second
+  field sat in the column meant for the move and remove buttons and the buttons wrapped
+  underneath. Fields now stack and the buttons sit beside the first. The form now places an
+  item's children itself (`grid-column`), so a stylesheet of your own that arranged
+  `.schema-item` children may need a look.
+- **Fixed: setting `value` with a different number of array items left the old rows.** A
+  longer array showed only the rows it had before, and a shorter one kept controls for items
+  that no longer existed. Arrays are now re-filled when their length changes.
+- **Fixed: a schema `title` that is not a string** was handed to the label, or to a union's
+  picker option, as element properties. Only a string is a title now, for properties and for
+  `anyOf` / `oneOf` branches; anything else falls back to the key or the branch's value.
+- Schema `title`s were already shown as written, never humanised or localized; the docs now
+  say so and a test holds it.
+
 ## 1.16.13
 
 Documentation only; no library code changed.