@vanelsas/baredom 3.10.0 → 3.12.0

package/CHANGELOG.md

@@ -2,6 +2,54 @@
 
 All notable changes to BareDOM will be documented in this file.
 
+## [3.12.0] - 2026-09-15
+
+### Added
+
+- **`x-file-download` saves through the native save dialog.** A new `picker` attribute makes a
+  click open `showSaveFilePicker`, so the user chooses the folder and the name. The component
+  then fetches `href` and streams it into the chosen file, and reports the outcome as
+  `x-file-download-success`, `x-file-download-cancel` or `x-file-download-error` with the failing
+  phase. Browsers without the API, such as Firefox, Safari and Brave, keep the plain download, as
+  do cross-origin frames and a dialog that cannot open. `picker` is off by default, so existing
+  pages are unchanged.
+
+  All five adapters gain the `picker` prop and the three events: `-react` 2.5.0, `-angular`
+  2.11.0, `-vue` 0.5.0, `-svelte` 0.5.0, `-solid` 0.5.0.
+
+## [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