Edgar Espina
Edgar Espina
How bad is to add method like @agentgt suggest to StatusCode? ```java return StatusCode.NOT_FOUND.throwIfNull(userRepository.findUserById(userId)) ``` Also: `throwIfFalse`, `throwIfTrue` etc... Or probably `assertXXX`?
> However, with return StatusCode.NOT_FOUND.... I'm afraid that we're shifting the focus away from the normal/positive flow and prioritizing the corner case of NOT_FOUND. It feels a bit odd to...
There is nothing yet in 3.x. We started a discussion last week: https://github.com/jooby-project/jooby/pull/3494
have a look at: https://jooby.io/#modules-validation
Make sense, send a PR we can work from there.
@SentryMan thank you. I feel here isn't necessary to add another abstraction over the jakarta one. Leaving jakarta-validator outside of core is enough.
Seems 3 it is OK. jooby-apt should call io.jooby.validation.BeanValidator and extra logic goes here (jooby-jakarta-validation) and probably on the jooby-avaje-validator module. So jooby-apt will do what is doing here, wrap...
oh yea, let me push the version bump
@kliushnichenko done
Thank you. Isn't any way to improve it?