Support openapi/jsonschema value constraints about tapir HOT 6 CLOSED

@tayvs yes, we are working on it. Should be ready in the nearest future, stay tuned :)

from tapir.

@adamw @ghostbuster91 Is there any updates?

from tapir.

@ghostbuster91 sorry for repeated pings, but are there new updates on this? This feature would be a big convenience for my team, so I'd be happy to help out with finishing it if there are pieces that could be split out.

from tapir.

No problem, I also think that this feature will be very convenient for everyone and would love to ship it. Luckily, recently I made almost complete implementation. It is still not merge-able since I was mostly experimenting and doing some shortcuts but I believe that it is something on which we can iterate. It would be great if you can take a look at #201 and give some feedback :)

from tapir.

As discussed here: https://gitter.im/softwaremill/tapir?at=5d5fb1d768406739f96b3712 I'm adding my use case. I'd like, on errors, to return the same jsonBody[JsonError] for various errors but different status codes to be a good HTTP/REST citizen. Ex:

    endpoint
      .post
      .in("auth" / "session")
      .in(jsonBody[LoginRequest])
      .out(oneOf(statusMapping(Created, jsonBody[LoginResponse.LoggedIn])))
      .errorOut(...)
      .serverLogic { request =>
        authService.login(request).map {
          case logged @ LoginResponse.LoggedIn(_, _) => Right(logged)
          case LoginResponse.InvalidCredentials => Left((Unauthorized, JsonError("Invalid credentials"))) // just an idea
          case LoginResponse.UserNotFound => Left((NotFound, JsonError("User not found"))) // just an idea
        }
      }

from tapir.

Released in 0.10.0
@luksow your comment moved to #208 :)

from tapir.