Closed paris0120 closed 2 years ago
could you please follow the issue template and provide more info. Issues like these are hard to reproduce for us
could you please follow the issue template and provide more info. Issues like these are hard to reproduce for us
Sorry. Updated.
Microservice without clientFramework is a traditional microservice.
Microservice without clientFramework is a traditional microservice.
If so why there is microfrontends value on the gateway server? Isn't it duplicated and conflicting? You can just keep one of them for microfontend, either microfrontends in the gateway or client framework in the microservice.
If we try to integrate applications config (which aren’t integrated) and you extract the application out of the jdl, the application looses information and is not reproducible. With microfrontends, you can generate each application separately (each has its own jdl).
commented
Then the microfontend option for gateway is duplicated. Gateway can decide to generate which entity with 'entities' option. One thing always bothering me is that if I want to update one application I have to either have a separate jdl file or generate all the applications. I'm wondering if you can add an argument for jdl to generate only one specific application from like 'jhipster jdl xxx.jdl -a blog'. Then we can have one single integrated jdl but can generate individual application from it and have a more consistent jdl structure.
Overview of the issue
If no framework is set for microservice, micro frontend won't generate.
Motivation for or Use Case
Micro frontend generation
Reproduce the error
There is no webapp folder generated for blog due to the lack of clientFramework value with the following jdl profile
Related issues
Suggest a Fix
Set a default client framework if it's not set (angularX?)
JHipster Version(s)
7.9.2
JHipster configuration
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryBrowsers and Operating System