Closed Tcharl closed 8 months ago
This issue is stale because it has been open for too long without any activity. Due to the moving nature of jhipster generated application, bugs can become invalid. If this issue still applies please comment otherwise it will be closed in 7 days
Overview of the feature request
I propose to modify the jdl's options to have something more clear for the end user in a microservice/gateway configuration.
The thing would be to introduce a new application option:
routed
and get rid of themicroservice
option. It also implies an adjustment of theentities
option spec.It would lead to this kind of jdl:
Note that these options won't handle the only routing and no frontend at the gateway level. A way to handle this use case would be to separate
entities
option intofrontendEntities
andbackendEntities
and let therouted
option only in charge of the routing. Still, this change looks too heavy to introduce.Your thought?
Motivation for or Use Case
The
microservice
and theentities ... with
options' behavior as they are design designed today are quite difficult to grab because they behaves differently depending on their contexts:backend routing
if the option is located/targeting a gateway orgenerated
when the context is a ms