Closed mraible closed 4 years ago
@pascalgrimaud I created a "reactive" label, but then realized maybe it should be named "theme: reactive"?
yes, theme: reactive
is better to keep consistency. I'm surprised that it didn't exist yet
FYI, unless someone else is already working on it, I'll try to handle this task.
I'm not sure you can assign the work to yourself if there's a bounty on it :smiley: . Anyway please go ahead. I at least won't try to compete on this.
@cbornet : I'm just trying to avoid duplicated effort, and thus announcing that I'm currently working on it (https://github.com/murdos/generator-jhipster/tree/reactive-entity-server). I'll open a draft when I got a full use case complete (e.g. entity without service).
But I see your point, I've unassigned myself from the ticket.
BTW I've started working on SQL/R2DBC support. For the entity gen you can maybe ignore SQL for now.
@murdos Are you still planning to add support for Elasticsearch? Also, did you get the bounty for this?
Are you still planning to add support for Elasticsearch?
Yes. I got something working at last. I need to report the changes to the templates, you should have a PR during the week to come.
Also, did you get the bounty for this?
Not yet.
Regarding r2dbc entity support, I'm inclined to wait the availability of https://github.com/spring-projects/spring-data-r2dbc/issues/282 in a milestone before really starting, it should really ease the work (and also simplify the existing User and PersistenceAuditEvent r2dbc repositories).
Also I noted that R2DBC support has been added in Spring Boot 2.3 M3, so the experimental spring boot starter is now deprecated (or at least not updated it seems) and there are some breaking changes that we'll need to handle.
Overview of the feature request
One of the last remaining items to move our Reactive/WebFlux support (https://github.com/jhipster/generator-jhipster/issues/7608) to beta is to update the entity generator and its tests.
WebTestClient
Motivation for or Use Case
I'm opening these tasks as a new issue so we can assign a bug bounty to it and hopefully accelerate its development. Selfishly, I'd like to demo our WebFlux support with microservices in March.
Related issues or PR