Describe, Then Interpret: HTTP Endpoints Using Tapir

There’s no shortage of great HTTP server libraries in Scala: akka-http, http4s, play, finch, just to name some of the more popular ones. However, a common pain point in all of these is generating documentation (e.g. Swagger/ OpenAPI).

Some solutions have emerged, such as annotating akka-http routes, generating scale code from YAML files or … writing YAML documentation by hand. But let’s be honest. Nobody wants or should be writing YAML files by hand, and annotations have severe drawbacks. What’s left then?

from DZone.com Feed https://ift.tt/2XpwOpe