Skip to content

Update @whatsaaaa packages - #11

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/@whatsaaaa-packages
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/@whatsaaaa-packages

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
@whatsaaaa/design-system 0.8.1 → 0.8.2 age confidence
@whatsaaaa/form-builder-react (source) 1.0.0-rc.0 → 1.0.0-rc.3 age confidence
@whatsaaaa/form-builder-schema (source) 1.0.0-rc.0 → 1.0.0-rc.3 age confidence
@whatsaaaa/form-builder-vue (source) 1.0.0-rc.0 → 1.0.0-rc.3 age confidence

Release Notes

whatsaaaa/design-system (@​whatsaaaa/design-system)

v0.8.2

Compare Source

Patch Changes
  • #​27 ffff150 Thanks @​whatsaaaa! - The path of the docs theme's status line gives way the way 0.8.1's does. The docs theme put the file in the status line without ws-status-line__path, so it never had the rules 0.8.1 added for it: on a docs site the path showed down to one character and then a bare ellipsis below about 242 px, and the status line reached past the window at 198 px and narrower. It is cut with an ellipsis down to five characters now and goes as a whole with less room, never a stub, and the status line fits at every width a phone has. From 320 px up it looks as it did. A site on the docs theme takes this with no change of its own.
whatsaaaa/form-builder (@​whatsaaaa/form-builder-react)

v1.0.0-rc.3

Compare Source

Minor Changes
  • #​83 9820092 Thanks @​whatsaaaa! - useJsonForm runs the fills of the definition, like the fills of @whatsaaaa/form-builder-fills: each new value of a trigger sets the fields of its fill, and a trigger that loses its value blanks them. The values of a map are in the initial input on the first render, and the fills of sources the form starts with run once it is mounted, as values it starts with, so the form isn't dirty. A trigger that initialInput has a key for fills nothing as the form starts. jsonForm.fills says what waits for a source, pending and isPending(path), and is a new object only when that changes, so disable the submit button while fills.pending isn't empty. Each value field component gets a pending prop in a form with fills. The new option onFillError gets each error of a fill, with the trigger and its value, and without it the error is thrown like an uncaught one. Next and goTo() forward wait for pending fills before they validate, and move among the steps on show for the values the fills set. jsonForm.reset() resets the whole form, like Formisch's reset with the same options but keepInput, with an initialInput that goes over the definition's defaults like the option's, and starts the fills again, as when the form was mounted, so the next value sets every field the user hasn't edited since, and the steps from the first one. FillsState and FillErrorInfo are exported. Every rule is in https://whatsaaaa.github.io/form-builder/frameworks/react#fills.
Patch Changes

v1.0.0-rc.2

Compare Source

Patch Changes
  • #​61 cc0ae9a Thanks @​whatsaaaa! - In a form with steps, the errors your submit handler sets with Formisch's setErrors, like the messages of a server that rejects the input, now stay on their fields. Before, they were gone at once: after a submit that left errors, the steps validated the form again to find the step to go back to, which put the schema's result over them. The steps now read the errors the form has. A message on a field of an earlier step takes the user back to that step, with the field focused, like a form rule that fails there. The form's own error from a submit handler that throws stays too. The user's next edit still validates the form again, as in a form without steps.

v1.0.0-rc.1

Compare Source

Minor Changes
  • #​58 7b8a4e4 Thanks @​whatsaaaa! - useJsonForm takes initialInput: the values the form starts with, like a record to edit. They go over the definition's defaults, so a field without a key keeps its default, in groups and in the items of lists too, and a key that is there wins, so undefined starts a field blank. Pass the input of the old form to keep what the user typed when you build the form again with a new key, like for another language. With useJsonForm<TInput>() it is typed by your input type, with every key optional. UseJsonFormOptions has a type parameter for that, the form's schema, which defaults to BuiltSchema. Every rule is in https://whatsaaaa.github.io/form-builder/api/react/UseJsonFormOptions#initial-input.
whatsaaaa/form-builder (@​whatsaaaa/form-builder-schema)

v1.0.0-rc.3

Compare Source

Patch Changes
  • #​83 ce2e6e0 Thanks @​whatsaaaa! - After run.stop(), run.start() runs again each fill the stop cancelled whose trigger still has the value it ran for, the fill of a change too, not only those the form starts with. A renderer that stops the run and starts it again, like React's StrictMode, or an <Activity> that hides the form and shows it again, no longer drops a fill that was waiting for a source.

v1.0.0-rc.2

Compare Source

Minor Changes
  • #​88 482379a Thanks @​whatsaaaa! - FillsRun has reset(), to call after the form is reset, like with Formisch's reset. It starts the fills again on the input the form holds, as open() and start() do: it aborts every pending call, each trigger's value counts as handled and no field as edited, so the next value sets every field the user hasn't changed since, and once the form is started, the fills of each trigger that starts from its default run again, as starting values. Pass given when the reset gives the form another initial input: a trigger it has a key for fills nothing, and no fill sets a field it has a key for as the form starts.

v1.0.0-rc.1

Compare Source

Minor Changes
  • #​71 34bf706 Thanks @​whatsaaaa! - Extensions can fill fields from the value of another: ctx.fill(trigger, fill) adds a fill on a field, and each new value of that field sets the fields the fill names, with values the definition holds, like a map, or that come later, like from a server. builder.getFills(json) runs them in a form, in any framework: open() them on the form's getInput, setInput and setStartInput, start() the run once the form is on the page, and call update() after each change of the input. A fill sets only the fields the user hasn't edited since the last fill, unless its overwrite is 'always', and fits each value to its field. A new value of the trigger aborts the call before it through its AbortSignal, and a trigger that loses its value blanks every field its fill sets. As the form starts, a fill runs only for a trigger that starts from its default, never for one the app's initial input gives, so a saved record keeps its values, and getInitialInput() has the values of the fills written in the definition. run.state says what is pending, and errors go to onError. Fills that set each other's triggers in a loop are a cycle issue, and the new issue code unknown_source is for a source of values an extension doesn't know. ResolvedField has the field's role. The new types are Fills, FillsForm, FillsRun, FillsState, OpenFillsOptions, FillErrorInfo, TargetFill, FillContext, FillResult and FillTriggerValue. Every rule is in https://whatsaaaa.github.io/form-builder/guide/extensions#fills.
whatsaaaa/form-builder (@​whatsaaaa/form-builder-vue)

v1.0.0-rc.3

Compare Source

Minor Changes
  • #​88 ae21b1f Thanks @​whatsaaaa! - useJsonForm runs the fills of the builder's extensions, like the fills of @whatsaaaa/form-builder-fills: each new value of a field with fills, like a profile picked from a select, sets the fields it names with Formisch's setInput. A field that starts from its default fills in the others as the form starts: the values of a map are in the initial input, and those of a source are set once the form is mounted, as the values it starts with, so it isn't dirty. A field the initialInput option has a key for fills nothing as the form starts, so a saved record keeps its values. jsonForm.fills says what is pending, to disable the submit button while values are on their way, each value field gets a pending prop in a form with fills, and the steps' Next waits for pending fills before it validates. jsonForm.reset() resets the whole form, like Formisch's reset with the same options but keepInput, with an initialInput that goes over the definition's defaults like the option's, and starts the fills again, as when the form was mounted, so the next value sets every field the user hasn't edited since, and the steps from the first one. The new onFillError option gets each error of a fill, with its trigger and value; without it, the error is thrown like an uncaught one. Unmounting the form aborts the calls of its sources. FillsState and FillErrorInfo are exported. Every rule is in https://whatsaaaa.github.io/form-builder/frameworks/vue#fills.
Patch Changes

v1.0.0-rc.2

Compare Source

Patch Changes
  • #​61 cc0ae9a Thanks @​whatsaaaa! - In a form with steps, the errors your submit handler sets with Formisch's setErrors, like the messages of a server that rejects the input, now stay on their fields. Before, they were gone at once: after a submit that left errors, the steps validated the form again to find the step to go back to, which put the schema's result over them. The steps now read the errors the form has. A message on a field of an earlier step takes the user back to that step, with the field focused, like a form rule that fails there. The form's own error from a submit handler that throws stays too. The user's next edit still validates the form again, as in a form without steps.

v1.0.0-rc.1

Compare Source

Minor Changes
  • #​58 7b8a4e4 Thanks @​whatsaaaa! - useJsonForm takes initialInput: the values the form starts with, like a record to edit. They go over the definition's defaults, so a field without a key keeps its default, in groups and in the items of lists too, and a key that is there wins, so undefined starts a field blank. Pass the input of the old form to keep what the user typed when you build the form again with a new :key, like for another language. With useJsonForm<TInput>() it is typed by your input type, with every key optional. UseJsonFormOptions has a type parameter for that, the form's schema, which defaults to BuiltSchema. Every rule is in https://whatsaaaa.github.io/form-builder/api/vue/UseJsonFormOptions#initial-input.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/@whatsaaaa-packages branch from 42161f8 to 318b267 Compare November 16, 2026 15:41
@renovate renovate Bot changed the title Update @whatsaaaa packages to v1.0.0-rc.2 Update @whatsaaaa packages Nov 16, 2026
@renovate
renovate Bot force-pushed the renovate/@whatsaaaa-packages branch from 318b267 to 7a34424 Compare November 17, 2026 11:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants