Fix pre-existing ty diagnostics in a second batch of test files

Same isinstance/cast narrowing and Optional-field assert pattern as the
prior commits, covering the airconditioner, fridge, washer, operational,
subdevices, sensor_hysteresis, laundry, select_options, identity and
entities test files.
This commit is contained in:
Marc Billow committed 2026-08-03 00:11:05 +00:00
1 parent 07061c734d
commit 36a642135b
17 files changed
+322 -100

No files matched your search

+8 -1
View File
@@ -20,7 +20,13 @@ def test_value_fn_defaults_to_identity():
def test_descriptions_are_frozen():
d = SensorDesc(key="power", field="f")
try:
d.key = "other"
# setattr() through a variable name (not `d.key = "other"`, and not a
# literal setattr(d, "key", ...) -- ruff's B010 rewrites that back to
# attribute-assignment syntax), so this reaches the same
# frozen-dataclass __setattr__ at runtime without ty statically
# flagging the (deliberately illegal) direct attribute assignment.
attr = "key"
setattr(d, attr, "other")
except Exception as e:
assert "frozen" in str(type(e)).lower() or "cannot" in str(e).lower()
else:
@@ -46,4 +52,5 @@ def test_select_carries_options_and_write_fn():
options=("voice", "tone", "mute"),
write_fn=lambda p, rep: (["settings", "sound", "mode", "vs", "0"], {"mode": p}),
)
assert d.write_fn is not None
assert d.write_fn("tone", {}) == (["settings", "sound", "mode", "vs", "0"], {"mode": "tone"})