@vanelsas/baredom 3.9.0 → 3.11.0

package/CHANGELOG.md

@@ -2,6 +2,73 @@
 
 All notable changes to BareDOM will be documented in this file.
 
+## [3.11.0] - 2026-08-28
+
+### Fixed
+
+- **Event detail keys are published as the component dispatches them.** `x-particle-button`
+  dispatches `#js {:press-x … :press-y …}`, so those are the keys on the event, but the generated
+  types camel-cased them and promised `pressX` and `pressY`. Every typed caller read a field that
+  is not there. The `.d.ts`, `custom-elements.json` and all five adapters now say `"press-x"`,
+  quoted because a hyphenated key is not a bare identifier in a TypeScript type.
+
+  This supersedes the detail half of the 3.3.0 fix "TypeScript declarations", which corrected the
+  same invalid identifiers by renaming them. That made the types compile and made them wrong.
+  Property names are unaffected and still camel-case, because a property reflects an attribute and
+  genuinely changes spelling.
+
+  Breaking for anyone writing `e.detail.pressX` — which never resolved to anything. Only
+  `x-particle-button` is affected; no other component has a kebab-case detail key. Every adapter
+  published the wrong key, so all five are released with it: `-react` 2.4.1, `-angular` 2.10.1,
+  `-vue` 0.4.2, `-svelte` 0.4.2, `-solid` 0.4.1.
+
+### Added
+
+- **`detail` on every event in `custom-elements.json`** — what an event carries, as data, beside
+  the TypeScript in `type.text`. A reader no longer parses a type expression to learn the shape.
+  Both come from one function, so they cannot disagree.
+
+### Changed
+
+- **`scripts/check_event_api.bb` also compares the manifest with the model.** It read the model on
+  both sides, so anything the generator did between them was invisible — which is how the
+  camel-casing above survived it. It now compares names and types over the union of both sides, so
+  a schema edited without regenerating is caught too.
+
+## [3.10.0] - 2026-08-28
+
+### Changed
+
+- **`x-date-picker` change details are one shape in both modes.** `x-date-picker-change` and
+  `x-date-picker-change-request` carried a different key set per mode — `value` in single mode,
+  `start` and `end` in range mode, and `date` on a range click — while `event-schema` declared only
+  the first. Every key is now always present and `null` where the mode has nothing to say, so the
+  declaration is true and a handler null-checks instead of testing for a key that was never there.
+
+  This widens the published types from `string` to `string | null` for `value`, `date`, `start` and
+  `end` on those two events, in `custom-elements.json`, the `.d.ts` files and all five framework
+  adapters. A consumer writing `const v: string = e.detail.value` will need a null check. Nothing
+  about when the events fire has changed.
+
+### Fixed
+
+- **The Svelte and Vue adapters no longer write `"null"` into a bound value.** Released as
+  `@vanelsas/baredom-svelte` 0.4.1 and `@vanelsas/baredom-vue` 0.4.1. Both coerced the
+  change detail unconditionally — `String(detail.value)`, `Number(detail.page)` — so a detail field
+  that did not apply arrived as the literal string `"null"` in `bind:value` / `v-model` and was
+  written back onto the element as an attribute. They now write only when the field is present.
+  `false`, `0` and `""` are values and still write; only `null` and `undefined` are skipped.
+  Affects the twelve form controls in each adapter. React, Solid and Angular do not write back and
+  were never affected.
+
+### Added
+
+- **`scripts/check_event_api.bb`** — a CI check that reads each component's dispatch calls and
+  asserts the manifest's event details agree with them. It reads forms rather than text, follows a
+  detail through a `let`, a helper, a namespace alias and `clj->js`, and reports what it could not
+  read rather than counting it as agreement. 198 of 201 events are compared; the three it cannot
+  resolve are named. It is what found the `x-date-picker` mismatch above.
+
 ## [3.9.0] - 2026-08-26
 
 The manifest declares `schemaVersion 1.0.0` and omitted three fields the schema defines. It now