diff options
| author | Sho Sakuma <me@m1sk9.dev> | 2026-08-30 20:43:18 +0900 |
|---|---|---|
| committer | Sho Sakuma <me@m1sk9.dev> | 2026-08-30 20:43:18 +0900 |
| commit | 64197733346bbcabc3daa65f6648c1a21e26b328 (patch) | |
| tree | 63d67ead1a9cd7460096e5dfa2977844d9f2e564 /website/src | |
| parent | 44132f3a73651fbd334a314fbc4ab47f5f1bbd5b (diff) | |
| download | LunaticChat-64197733346bbcabc3daa65f6648c1a21e26b328.tar.gz LunaticChat-64197733346bbcabc3daa65f6648c1a21e26b328.tar.bz2 LunaticChat-64197733346bbcabc3daa65f6648c1a21e26b328.zip | |
feat(engine): give both platforms one debug switch to read
"Debug" had grown into three unconnected mechanisms: a boolean injected into
RomanjiConverter, a one-off configuration dump at startup, and KtorSimpleLogger
calls that Paper's stock log4j configuration never printed. Turning `debug: true`
on told an operator nothing about the Velocity handshake, which is what #228 is
actually about.
The vocabulary goes in engine because it is a contract before it is an
implementation: config.yml and the proxy's system property have to agree on what
`velocity,protocol` means, and a category added on one side must exist on the
other. Only the writing is left to the platforms.
The message is a lambda so that the chat path - instrumented once per message -
costs nothing while debugging is off. The `if (debugMode) logger.info("... $word")`
guards this replaces built their strings either way.
Both platform loggers write at INFO rather than at the level the content
deserves, because neither Paper's nor Velocity's stock logging configuration
prints anything below it, and asking operators to edit log4j before they can
answer a bug report is the friction this exists to remove.
Refs #228
Co-Authored-By: Claude <noreply@anthropic.com>
Diffstat (limited to 'website/src')
0 files changed, 0 insertions, 0 deletions
