diff options
| author | Sho Sakuma <me@m1sk9.dev> | 2026-08-03 15:09:58 +0900 |
|---|---|---|
| committer | Sho Sakuma <me@m1sk9.dev> | 2026-08-05 01:15:29 +0900 |
| commit | fd56ebaa1dc2cfa8f834edb06395e8fc02375d1d (patch) | |
| tree | 7feb02881ca767e9180aafd6478be9a0d5c363af /platform-velocity | |
| parent | f4bff879ac2f4323011d41e4f7ee85a9695515a5 (diff) | |
| download | LunaticChat-fd56ebaa1dc2cfa8f834edb06395e8fc02375d1d.tar.gz LunaticChat-fd56ebaa1dc2cfa8f834edb06395e8fc02375d1d.tar.bz2 LunaticChat-fd56ebaa1dc2cfa8f834edb06395e8fc02375d1d.zip | |
refactor: move romaji conversion out of engine
Closes #259.
engine exposed ktor through api(), so both platforms inherited the client
and its CIO engine. The only thing in engine that used ktor was
GoogleIMEClient, and the only module that used GoogleIMEClient was
platform-paper - Velocity was shipping roughly six megabytes of HTTP
client to support a Paper-only feature. Same story for
kotlinx-coroutines-core, which Velocity does not use at all.
Romaji conversion is a Paper feature, so the converter package now lives
in platform-paper alongside the ConversionCache and RomanjiConverter that
were already there. engine keeps kotlinx-serialization on api(), which is
genuine shared surface: the plugin messaging protocol is built on it.
The velocity shadow jar goes from 7,618,405 to 2,769,395 bytes, and no
longer contains io/ktor at all.
CacheData's tests were sitting inside engine's SettingsDataClassesTest,
which is unrelated to settings; they move with the class.
Co-Authored-By: Claude <noreply@anthropic.com>
Diffstat (limited to 'platform-velocity')
0 files changed, 0 insertions, 0 deletions