Daniel PETISME

Hi David, Sorry I misunderstood the fix. The Keycloak json are inherited from https://github.com/jhipster/generator-jhipster/tree/main/generators/docker-compose/templates/realm-config JHipster Quarkus is not maintaining them, the PR should be made to the upstream repo. I...

Are you sure it can only be solved by a realm update ? I mean, if the json work fine with the upstream jhipster, maybe it's the Quarkus Java code...

Hi! You actually did the right thing! I re-triggered the tests because one was failing (most of the time it's a Maven downloading issue and not code related). If the...

🤔 I would like to avoid that as much as if possible... Upstream Jhipster and other blueprints (.Net, Node.JS) manage to solve the issue with adding a question, I think...

Hi @dminkovski I'm struggling to have a proper look at what you proposed. I'll do my best to give you a quick answer.

Hi! I feel sorry to say I didn't spend any time on this PR... #shame In a Quarkus context, Oauth2 works nice with Angular so I don't understand why it...

Hi @dminkovski You're right. As for now, the Quarkus blueprint does not provide the JHipster microservice pattern. This is a choice I made on purpose. I'm not sure there is...

I would build the sort object before invoking the method (just as the Page object).

You right, is 100% templates. Couple of pointers: https://quarkus.io/guides/reactive-routes https://quarkus.io/guides/reactive-sql-clients Quarkus "reactivity" relies on Vert.x but there is a "callback-free" API for the Web layer so I propose to focus...

Moving to reactive is a major step. Where web and service are quite easy to migrate, data is way more tricky. As for now, Quarkus does not provide a "reactive"...