From ebdb8d1940b41bab60d201eb6b0cd6f05efbc6ac Mon Sep 17 00:00:00 2001 From: Sho Sakuma Date: Sun, 30 Aug 2026 13:48:54 +0900 Subject: docs(paper): say why the non-YamlException catch has no test It shows up as an uncovered line on every patch that touches parse(), and the next reader would otherwise have to rediscover that no config.yml can reach it. Co-Authored-By: Claude --- .../main/kotlin/dev/m1sk9/lunaticChat/paper/config/ConfigManager.kt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/platform-paper/src/main/kotlin/dev/m1sk9/lunaticChat/paper/config/ConfigManager.kt b/platform-paper/src/main/kotlin/dev/m1sk9/lunaticChat/paper/config/ConfigManager.kt index 35d19a3..58b1df2 100644 --- a/platform-paper/src/main/kotlin/dev/m1sk9/lunaticChat/paper/config/ConfigManager.kt +++ b/platform-paper/src/main/kotlin/dev/m1sk9/lunaticChat/paper/config/ConfigManager.kt @@ -158,7 +158,8 @@ class ConfigManager( document = remaining } catch (e: Exception) { // A serializer can fail without kaml turning it into a YamlException, and there is - // no path to prune a single setting by without one. + // no path to prune a single setting by without one. No config.yml reaches this - + // only a serializer bug does - so it is deliberately left without a test. return ParseOutcome.Undecodable(UNREADABLE, e) } } -- cgit v1.2.1