Peter Taoussanis e6ce33dd4e [mod] SLF4J->Telemere backend: move noisy stuff out of signal data ... This is a BREAKING change for the small minority of users that: 1. Are using the `taoensso.telemere.slf4j` backend, AND 2. Are using the low-level `:slf4j/args` or `:slf4j/marker-names` values in signal `:data` BEFORE this commit: SLF4J signals contain: {:data {:slf4j/kvs {...}, :slf4j/args [...], :slf4j/marker-names #{...}}, ...}. AFTER this commit: SLF4J signals contain: {:data {:slf4j/kvs {...}}, :kvs {:slf4j/args <Object[]>, :slf4j/markers #{...}}, ...} So: - [:data :slf4j/marker-names] has moved to [:kvs :slf4j/markers]. - [:data :slf4j/args] has moved to [:kvs :slf4j/args], and is now an Object[] rather than vector. Motivation for the change: The new behaviour is a more sensible default. Basically: anything in `:data` is included by default in output. But :slf4j/args are generally anyway already in the signal's formatted message, so this ends up just creating duplicate output. Likewise markers are generally used more for filtering/xfns than for output labelling, so excluding them from default output is sensible.		2025-12-04 21:13:37 +01:00
..
graal_tests.clj	[nop] Simplify dir structure	2025-01-14 10:35:25 +01:00
telemere_tests.cljc	[mod] SLF4J->Telemere backend: move noisy stuff out of signal data	2025-12-04 21:13:37 +01:00