problem-details-ktor-validation

Ktor RequestValidation plugin integration: maps RequestValidationException to a Problem carrying an errors[] extension array with JSON Pointer (RFC 6901) references — the multi-field validation pattern RFC 9457 itself recommends.

RequestValidation's own ValidationResult.Invalid carries nothing but a flat list of reason strings — no field name, no path. io.github.ilyankin.rfc9457.ktor.validation.invalidField and io.github.ilyankin.rfc9457.ktor.validation.invalidFields encode a JSON Pointer alongside each message so io.github.ilyankin.rfc9457.ktor.validation.requestValidation can decode it back into a proper errors[] entry; a reason written any other way still works, it just degrades to a detail-only entry with no pointer.

Packages

common

Published for jvm, js, wasmJs, linuxX64, linuxArm64, mingwX64, macosArm64, iosArm64 and iosSimulatorArm64. Depend on the plain coordinates from commonMain and Gradle picks the variant.