@keenmate/web-multiselect 2.0.0-rc01 → 2.0.0-rc02

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -21,6 +21,21 @@ Reads `--base-*` variables from the page if [`@keenmate/theme-designer`](https:/
21
21
  - Custom rendering callbacks for options, badges, and group headers.
22
22
  - Form integration via standard hidden inputs (FormData-compatible).
23
23
 
24
+ ## What's New in v2.0.0-rc02
25
+
26
+ **Form association restored for host frameworks (`el.form`).** Selecting inside a
27
+ `<web-multiselect>` that lives in a `<form>` again delivers changes to frameworks
28
+ that resolve the parent form via `event.target.form` — most notably Phoenix
29
+ LiveView's `phx-change` delegation, which silently dropped changes in rc01.
30
+ `<web-multiselect>` is a form-associated custom element, so it now exposes a real
31
+ `el.form` / `event.target.form` like a native control. (rc01 had hardened its
32
+ internal `ElementInternals` handle to a true `#private` field, which killed the
33
+ `.form` that host-framework wrappers read.) The fix lives upstream in
34
+ [`@keenmate/web-components-core`](https://www.npmjs.com/package/@keenmate/web-components-core)
35
+ 1.0.0-rc02 (the `el.form` getter), which this release pins.
36
+
37
+ See `CHANGELOG.md` for the full list.
38
+
24
39
  ## What's New in v2.0.0-rc01
25
40
 
26
41
  **The core-adoption major.** `<web-multiselect>` is now built on
@@ -115,6 +130,32 @@ npm install @keenmate/web-multiselect
115
130
 
116
131
  See [docs/usage.md](./docs/usage.md) for the full API and [docs/examples.md](./docs/examples.md) for advanced patterns (async data, virtual scrolling, custom rendering, form integration).
117
132
 
133
+ ## Editor IntelliSense
134
+
135
+ The package ships editor metadata so you get autocomplete and hover docs for the
136
+ element's attributes, events, and all `--ms-*` CSS custom properties. All of it is
137
+ generated from the component's source on every build, so it never drifts.
138
+
139
+ - **JetBrains** (WebStorm / IntelliJ) — works automatically. The IDE discovers
140
+ `web-types.json` via the `web-types` field in `package.json`; no setup needed.
141
+ - **VS Code** — the data files ship but VS Code doesn't auto-discover them from a
142
+ dependency, so point your workspace at them once in `.vscode/settings.json`:
143
+
144
+ ```json
145
+ {
146
+ "html.customData": [
147
+ "./node_modules/@keenmate/web-multiselect/vscode.html-custom-data.json"
148
+ ],
149
+ "css.customData": [
150
+ "./node_modules/@keenmate/web-multiselect/vscode.css-custom-data.json"
151
+ ]
152
+ }
153
+ ```
154
+
155
+ `html.customData` powers tag/attribute completion on `<web-multiselect>`;
156
+ `css.customData` powers completion for the `--ms-*` theming variables. Reload
157
+ the window after adding them.
158
+
118
159
  ## Browser support
119
160
 
120
161
  Modern evergreen browsers — anything with native `customElements`, Shadow DOM, and CSS `@layer` support:
@@ -2696,14 +2696,6 @@
2696
2696
  "text": "HTMLDivElement | undefined"
2697
2697
  }
2698
2698
  },
2699
- {
2700
- "kind": "field",
2701
- "name": "#internals",
2702
- "privacy": "private",
2703
- "type": {
2704
- "text": "ElementInternals | undefined"
2705
- }
2706
- },
2707
2699
  {
2708
2700
  "kind": "field",
2709
2701
  "name": "#customStyles",