Łukasz Witkowski

Superseded by #247

Hey @mraible, please bump `quarkus-resteasy-problem` to 3.9.0 here: https://github.com/jhipster/generator-jhipster-quarkus/blob/quarkus-3.9/generators/quarkus/templates/pom.xml.ejs#L52 This should fix some (maybe even all) failed builds. Unfortunately our extension is not part of Quarkiverse (yet) so this version...

Hi @bdunni, it may seem weird, but hibernate validator puts controller's class name and method name as first 2 elements of the property path - we decided we don't want...

@NissenDev @bdunni thanks for reproducer, now I see that you use Validator programmatically, instead of simply using @Valid annotation on `Book` request param. `@Valid` usage is covered with tests, and...

@bdunni support for validation groups is a nice feature request, I've never used them. I'll try have a closer look. Regarding original issue, after merging #313 we could add a...

> However what if they were to use the constraints programatically and from the annotation? Wouldn't this be an issue? When you opt-in for not sanitizing parameters, you'll get everything...

No, it would never ignore anything if this flag is active - it would work similar to default Quarkus implementation. The consequence would be that Class and method name will...

Hi @rkovarik, you are not wrong, but I don't think current implementation `violates the RFC` in any harmful way - nobody (not even RFC) expects this uri to be resolvable...