From f5fad1b2e6b26fbb8364347eb18f3b76e76207a8 Mon Sep 17 00:00:00 2001 From: LGUG2Z Date: Thu, 29 Oct 2026 09:17:54 -0700 Subject: [PATCH] docs(repo): the three ways kfw's placement type is described Its docs say a place is a string or an integer, its deserializer takes a string only, and its schema describes objects. Nothing tests the integer. --- docs/dev/BEHAVIOUR.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/dev/BEHAVIOUR.md b/docs/dev/BEHAVIOUR.md index 241f8f25..a4898f24 100644 --- a/docs/dev/BEHAVIOUR.md +++ b/docs/dev/BEHAVIOUR.md @@ -67,7 +67,9 @@ kfw the sweep now plugs in a second display first. number, makes `komorebi.exe` exit at start with `data did not match any variant of untagged enum InitialWindowPlacementRules`, while the string `"2"` works, and kfde accepts both. kfw's own docs for the type say an integer is accepted, but its `PlacementTarget` deserializes with -`String::deserialize`. It is a known failure to follow up on later: `placement.run` takes the +`String::deserialize`, nothing in kfw tests the integer form, and its `schema.json`, generated +from the enum rather than the hand-written deserializer, describes the type as objects +(`{"Placement": ...}` or `{"Index": n}`), which matches neither form. It is a known failure to follow up on later: `placement.run` takes the description of the case and the reason, and records the case that way, whether the daemon does not start or puts the windows elsewhere. The other four cases give the same order on both ports.