Hey Ktorians, I was using <https://tegral.zoroark....
# ktora
Aeden Jameson
05/19/2025, 3:40 PMHey Ktorians, I was using https://tegral.zoroark.guru/docs/modules/core/openapi/ for swagger/openapi functionality however the author doesn't anticipate working on the Tegral framework anytime soon. (e.g upgrading it to 3.x) I really like its ease of use and the DSL it had to decorate routes. What are some of the better options out there? I've looked around of course, but nothing stands out as being as straightforward.
r
RJ Garcia
05/20/2025, 4:10 AMhave you looked at https://github.com/SMILEY4/ktor-openapi-tools?
đź‘Ť 2
RJ Garcia
05/20/2025, 4:10 AMOur team has had some pretty good success integrating with that project for openapi integration ontop of ktor routes
a
Aeden Jameson
05/20/2025, 4:55 PM@RJ Garcia Thank you for this. I haven’t come across this one.
đź’Ş 1
r
RJ Garcia
05/20/2025, 4:56 PMya, it's pretty great, we've worked extensively with it and created custom plugins and such, it's very extendable
a
Anastasios Georgousakis
05/20/2025, 6:04 PMKtor 3 tegral support is on 0.0.5-SNAPSHOT. Unfortunately you have to use sonatype snapshots repository to get this artifact. I don’t know why the maintainer is not releasing it to maven central. Check https://github.com/utybo/Tegral/issues/100
a
Aeden Jameson
05/20/2025, 8:01 PM@Anastasios Georgousakis Good to know, but concerning for using it long term.
Aeden Jameson
05/23/2025, 5:05 PM@RJ Garcia I've started applying SMILEY4 and it's straightforward. The one thing I miss about Tegral is that its DSL was less invasive. e.g it didn't need to wrap the native
getr
RJ Garcia
05/23/2025, 6:19 PMnice, ya, we've been pretty happy with it. We initially found some issues related to generating discriminated unions to generate correctly, but we were able to submit some patches and create custom plugins that solved our needs, and it was honestly a good experience
a
Anastasios Georgousakis
05/23/2025, 6:38 PMI also started to migrate my endpoints to SMILEY4. It is almost the same, little more verbose but in a nice way. It also supports kotlinx serialization a feature that Tegral didn’t have. What i liked more with Tegral was that you describe the documentation at the end of route dsl so the implementation of the route which is more important was at the top of route dsl
r
RJ Garcia
05/23/2025, 6:53 PMya def agree that it creates more inline noise, but I also started defining each route as an individual named function instead of a bunch of route("") {} within a routing {} context which mitigated that readability issue and also made quick code navigation to specific routes a lot faster
2 Views