LGUG2Z 68c3133d4e refactor(protocol): use SocketMessage from komorebi-protocol in the Windows daemon ...

Delete the Windows SocketMessage, its as_bytes and FromStr (now in the crate) and re-export komorebi_protocol::message::SocketMessage from core, so komorebi::SocketMessage and komorebi_client::SocketMessage keep working. process_command stays an exhaustive match: the two KDE-only variants (ReloadHotkeys, HotkeysState) get one explicit arm that writes the 'not supported on this platform' reply (SocketMessage::not_supported_reply) and returns before anything else happens, so subscribers are not notified either. Behaviour change: those two used to fail to parse on Windows and now parse and are answered that way.

Verified: Windows clippy --workspace --locked --all-targets -D warnings clean; native cargo test -p komorebi-protocol passes. Windows unit tests and e2e not run (cannot on Linux).

2026-10-31 01:37:53 -07:00

..

src

refactor(protocol): use SocketMessage from komorebi-protocol in the Windows daemon

2026-10-31 01:37:53 -07:00

tests

feat(protocol): add the unified SocketMessage and the platforms() support table

2026-10-31 01:37:53 -07:00

Cargo.toml

refactor(protocol): use pathext from komorebi-protocol in KDE

2026-10-31 01:37:53 -07:00