v.0.5.3

try to fix the ui editor

v.0.5.2

fix: Editor dropdowns failing to update configuration on selection

- Switched listeners from `@selected` to a dual-binding of `@change` and `@closed` to support both legacy MWC and new Material 3 `<ha-select>` elements.
- Ensured `<mwc-list-item>` elements use string attributes (`value="x"`) instead of property bindings (`.value=${x}`) so `<ha-select>` correctly reads the selected option values.

v.0.5.1

fix: editor inputs failing to update configuration state

- Removed reliance on `configValue` DOM properties which were not persisting through Home Assistant UI components
- Implemented JS closures on event listeners (`@selected=${(ev) => this._valueChanged(ev, 'key')}`) to explicitly pass configuration keys
- Ensures all dropdowns, switches, and textfields sync properly with the card's config in the visual editor

v.0.5

fix: Lit property bindings for visual editor fields

- Fixed an issue where dropdowns and textfields in the visual editor failed to update the config
- Corrected Lit syntax for static property assignments from `.configValue=key` to `.configValue=${"key"}` to preserve camelCase property binding

v.0.4

refactor: apply DRY principles, standard error handling, and file org…

v.0.3

reuse ha-card and iframe to prevent reload on keystrokes

v.0.2

renamed vars from hex to something meaningfull

v.0.1

deobfuscated code