Repository navigation
Update @whatsaaaa packages - #11
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/@whatsaaaa-packages
branch
from
November 16, 2026 15:41
42161f8 to
318b267
Compare
renovate
Bot
force-pushed
the
renovate/@whatsaaaa-packages
branch
from
November 17, 2026 11:22
318b267 to
7a34424
Compare
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.
This PR contains the following updates:
0.8.1→0.8.21.0.0-rc.0→1.0.0-rc.31.0.0-rc.0→1.0.0-rc.31.0.0-rc.0→1.0.0-rc.3Release Notes
whatsaaaa/design-system (@whatsaaaa/design-system)
v0.8.2Compare Source
Patch Changes
ffff150Thanks @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 withoutws-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.3Compare Source
Minor Changes
9820092Thanks @whatsaaaa! -useJsonFormruns the fills of the definition, like thefillsof@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 thatinitialInputhas a key for fills nothing as the form starts.jsonForm.fillssays what waits for a source,pendingandisPending(path), and is a new object only when that changes, so disable the submit button whilefills.pendingisn't empty. Each value field component gets apendingprop in a form with fills. The new optiononFillErrorgets each error of a fill, with the trigger and its value, and without it the error is thrown like an uncaught one. Next andgoTo()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'sresetwith the same options butkeepInput, with aninitialInputthat 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.FillsStateandFillErrorInfoare exported. Every rule is in https://whatsaaaa.github.io/form-builder/frameworks/react#fills.Patch Changes
ce2e6e0]:v1.0.0-rc.2Compare Source
Patch Changes
cc0ae9aThanks @whatsaaaa! - In a form with steps, the errors your submit handler sets with Formisch'ssetErrors, 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.1Compare Source
Minor Changes
7b8a4e4Thanks @whatsaaaa! -useJsonFormtakesinitialInput: 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 itsdefault, in groups and in the items of lists too, and a key that is there wins, soundefinedstarts a field blank. Pass the input of the old form to keep what the user typed when you build the form again with a newkey, like for another language. WithuseJsonForm<TInput>()it is typed by your input type, with every key optional.UseJsonFormOptionshas a type parameter for that, the form's schema, which defaults toBuiltSchema. 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.3Compare Source
Patch Changes
ce2e6e0Thanks @whatsaaaa! - Afterrun.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.2Compare Source
Minor Changes
482379aThanks @whatsaaaa! -FillsRunhasreset(), to call after the form is reset, like with Formisch'sreset. It starts the fills again on the input the form holds, asopen()andstart()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. Passgivenwhen 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.1Compare Source
Minor Changes
34bf706Thanks @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'sgetInput,setInputandsetStartInput,start()the run once the form is on the page, and callupdate()after each change of the input. A fill sets only the fields the user hasn't edited since the last fill, unless itsoverwriteis'always', and fits each value to its field. A new value of the trigger aborts the call before it through itsAbortSignal, 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, andgetInitialInput()has the values of the fills written in the definition.run.statesays what is pending, and errors go toonError. Fills that set each other's triggers in a loop are acycleissue, and the new issue codeunknown_sourceis for a source of values an extension doesn't know.ResolvedFieldhas the field'srole. The new types areFills,FillsForm,FillsRun,FillsState,OpenFillsOptions,FillErrorInfo,TargetFill,FillContext,FillResultandFillTriggerValue. Every rule is in https://whatsaaaa.github.io/form-builder/guide/extensions#fills.whatsaaaa/form-builder (@whatsaaaa/form-builder-vue)
v1.0.0-rc.3Compare Source
Minor Changes
ae21b1fThanks @whatsaaaa! -useJsonFormruns the fills of the builder's extensions, like thefillsof@whatsaaaa/form-builder-fills: each new value of a field withfills, like a profile picked from a select, sets the fields it names with Formisch'ssetInput. A field that starts from itsdefaultfills in the others as the form starts: the values of amapare in the initial input, and those of asourceare set once the form is mounted, as the values it starts with, so it isn't dirty. A field theinitialInputoption has a key for fills nothing as the form starts, so a saved record keeps its values.jsonForm.fillssays what is pending, to disable the submit button while values are on their way, each value field gets apendingprop in a form with fills, and the steps' Next waits for pending fills before it validates.jsonForm.reset()resets the whole form, like Formisch'sresetwith the same options butkeepInput, with aninitialInputthat 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 newonFillErroroption 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.FillsStateandFillErrorInfoare exported. Every rule is in https://whatsaaaa.github.io/form-builder/frameworks/vue#fills.Patch Changes
482379a]:v1.0.0-rc.2Compare Source
Patch Changes
cc0ae9aThanks @whatsaaaa! - In a form with steps, the errors your submit handler sets with Formisch'ssetErrors, 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.1Compare Source
Minor Changes
7b8a4e4Thanks @whatsaaaa! -useJsonFormtakesinitialInput: 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 itsdefault, in groups and in the items of lists too, and a key that is there wins, soundefinedstarts 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. WithuseJsonForm<TInput>()it is typed by your input type, with every key optional.UseJsonFormOptionshas a type parameter for that, the form's schema, which defaults toBuiltSchema. Every rule is in https://whatsaaaa.github.io/form-builder/api/vue/UseJsonFormOptions#initial-input.Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.