Storm already ships Ktor integration; the 1.13.0 milestone tightens it. This issue covers request-level ergonomics.
Two small pieces. First, a route-scoped transaction helper, so a whole route or call runs inside one transaction {} without boilerplate in every handler. Second, documented StatusPages recipes mapping Storm exceptions to HTTP responses (unique key violation to 409, missing row to 404, and so on). Ktor has no platform exception hierarchy to translate into, so unlike the Spring side this is guidance rather than translation.
Tasks:
Storm already ships Ktor integration; the 1.13.0 milestone tightens it. This issue covers request-level ergonomics.
Two small pieces. First, a route-scoped transaction helper, so a whole route or call runs inside one
transaction {}without boilerplate in every handler. Second, documented StatusPages recipes mapping Storm exceptions to HTTP responses (unique key violation to 409, missing row to 404, and so on). Ktor has no platform exception hierarchy to translate into, so unlike the Spring side this is guidance rather than translation.Tasks: