Bump @codebar-ag/storybook from v1.13.0 to v1.21.0

[dependabot]

Bumps @codebar-ag/storybook from v1.13.0 to v1.21.0.

Release notes

Sourced from @​codebar-ag/storybook's releases.

v1.21.0

Added

• SearchableSelect accepts clearable (plus clear-label for the ✕'s accessible name, default "Clear selection"). While something is selected, an ✕ appears between the label and the chevron; pressing it emits update:modelValue with '' and hands focus back to the trigger.

  Without it the control is a trap for OPTIONAL values: it picks from a closed set and only ever emits option.value, so once anything is picked there is no gesture that returns to "nothing chosen". The consuming app hit this on its data-source form — the store-dialog field is nullable all the way down ('nullable' in the FormRequest, ?? null on submit), but a user who selected a dialog could never unselect it short of reloading the page. Its sibling controls both already had an exit: the native Select renders a selectable placeholder <option value="">, and Combobox is free text that can be erased. This closes the gap for the third sibling; required fields simply don't pass the prop.

  Two deliberate choices, so call sites don't pay for what they don't use:

  • Clearing emits '', not null — the same "nothing chosen" payload the native Select produces when its placeholder is picked. Emitting null would widen the payload type to T | null for every consumer, forcing null-handling onto the majority of call sites whose select is not clearable and can never receive it. (For a T = string site, T | '' collapses to string: existing handlers type-check unchanged.)
  • The ✕ is a sibling of the trigger, not a child — the trigger is itself a <button>, and a button inside a button is invalid HTML that browsers "repair" by splitting the elements apart. It is absolutely positioned into the trigger's right end at the control's full height, and only rendered while a selected option's label is actually on screen (a modelValue whose options have not arrived yet shows the placeholder, and there is nothing visible to clear).

  The Clearable story pins the loop: clear → model '', placeholder back, menu closed, focus on the trigger, ✕ gone; re-pick → ✕ back.

v1.20.0

No release notes provided.

v1.19.0

Four findings from the app that adopted 1.18.0, three of them acted on and one declined. One is a rendering bug that had been shipping for the life of the component: CodeEditor had no yaml mode and highlighted YAML as JSON without saying so.

This release adds a peer dependency. @codemirror/lang-yaml — see Upgrade notes. Nothing else here requires a change to a call site.

... (truncated)

Changelog

Sourced from @​codebar-ag/storybook's changelog.

v1.21.0

Added

• SearchableSelect accepts clearable (plus clear-label for the ✕'s accessible name, default "Clear selection"). While something is selected, an ✕ appears between the label and the chevron; pressing it emits update:modelValue with '' and hands focus back to the trigger.

  Without it the control is a trap for OPTIONAL values: it picks from a closed set and only ever emits option.value, so once anything is picked there is no gesture that returns to "nothing chosen". The consuming app hit this on its data-source form — the store-dialog field is nullable all the way down ('nullable' in the FormRequest, ?? null on submit), but a user who selected a dialog could never unselect it short of reloading the page. Its sibling controls both already had an exit: the native Select renders a selectable placeholder <option value="">, and Combobox is free text that can be erased. This closes the gap for the third sibling; required fields simply don't pass the prop.

  Two deliberate choices, so call sites don't pay for what they don't use:

  • Clearing emits '', not null — the same "nothing chosen" payload the native Select produces when its placeholder is picked. Emitting null would widen the payload type to T | null for every consumer, forcing null-handling onto the majority of call sites whose select is not clearable and can never receive it. (For a T = string site, T | '' collapses to string: existing handlers type-check unchanged.)
  • The ✕ is a sibling of the trigger, not a child — the trigger is itself a <button>, and a button inside a button is invalid HTML that browsers "repair" by splitting the elements apart. It is absolutely positioned into the trigger's right end at the control's full height, and only rendered while a selected option's label is actually on screen (a modelValue whose options have not arrived yet shows the placeholder, and there is nothing visible to clear).

  The Clearable story pins the loop: clear → model '', placeholder back, menu closed, focus on the trigger, ✕ gone; re-pick → ✕ back.

v1.19.1

Fixed

• Combobox opens on focus even when its options have not arrived yet. The focus handler was open = filtered.length > 0, so a click into the field opened the list only if options were already present — and nothing reopened it when they arrived later. For a static list that is invisible; for the remote-search shape, where a consumer replaces options with each debounced response, it is a race between the click and the first response. The user who loses it clicks into the field, sees nothing, and only typing

... (truncated)

Commits

• d0e183d Merge pull request #29 from codebar-ag/fix/searchable-select-clearable
• 81629c7 Let an optional SearchableSelect be cleared again
• 615c74d Merge pull request #28 from codebar-ag/fix/combobox-opens-before-remote-optio...
• 46d19e0 1.19.1 — the number the version gate asks for
• 5fbfb4c Combobox: open on focus even when the options have not arrived yet
• 87c4c75 Merge pull request #27 from codebar-ag/release/v1.19.0
• ac4ff96 1.19.0 — a real yaml mode, and the two diagnostics that were compiled away
• 0260c5f Merge pull request #26 from codebar-ag/release/v1.18.0
• 295994d Release 1.18.0, and guard the version before a tag can exist
• b4dd7e1 Every array a component accepts is readonly
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)