mirror of
https://github.com/Matysh/houseplan-card
synced 2026-07-31 08:28:31 +00:00
Matysh
3d41fe16b8
The device editor has offered display='value' since v1.26.0; MARKER_SCHEMA accepted only badge/ripple/icon_ripple. Picking it produced not a valid value for dictionary value @ data['config']['markers'][n]['display'] and since one rejected marker fails the whole config write, the user could not save the plan at all until the setting was undone. Reported by @RemyRoux with the exact error text, 2026-07-27 — a year and a half after the feature shipped. The schema now accepts it, and the class of bug is closed rather than the instance: DISPLAY_MODES, TAP_ACTIONS, SPACE_FILL_MODES and ROOM_FILL_MODES are exported from src/logic.ts, the editors render their options from them, and a backend test parses those lists out of the TypeScript source and asserts the schema accepts every one (and rejects a bogus value). Reverting the one-word schema fix fails that test, which is the check that was missing. Plus an HA-harness test saving a config that contains a value-display marker — the exact call the user's card was making. Docs: CHANGELOG.md + CHANGELOG.ru.md + TESTING.md + STATUS.md.
21 lines
456 B
JSON
Executable File
21 lines
456 B
JSON
Executable File
{
|
|
"domain": "houseplan",
|
|
"name": "House Plan",
|
|
"codeowners": [
|
|
"@Matysh"
|
|
],
|
|
"config_flow": true,
|
|
"dependencies": [
|
|
"http",
|
|
"frontend",
|
|
"websocket_api"
|
|
],
|
|
"documentation": "https://github.com/Matysh/houseplan-card",
|
|
"integration_type": "service",
|
|
"iot_class": "local_push",
|
|
"issue_tracker": "https://github.com/Matysh/houseplan-card/issues",
|
|
"requirements": [],
|
|
"single_config_entry": true,
|
|
"version": "1.45.3"
|
|
}
|