Customize JHipster 7 features.

[mshima]

• Change user api endpoint from /api/users to /api/admin/users.
• Rename jdl samples from .jh to .jdl
• Reformat workflows to tabWith 2 to match jhipster main repository format.
• Add cypress to samples, disable failing tests.
• Customize package.json scripts.

related to #223

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[avdev4j]

not sure to understand why we need to change the users endpoint.
I plan to do a new beta release including JHipster 7, I guess this one should be included.

[mshima]

Or customize endpoints at clients:
https://github.com/jhipster/generator-jhipster/blob/aa9f3475582d7e4e751eb8ee1f7775762ccc2ebc/generators/client/templates/angular/src/main/webapp/app/admin/user-management/service/user-management.service.ts.ejs#L33

[mshima]

@avdev4j do you prefer to change the client endpoint instead?

[avdev4j]

as I understand we changed the endpoints generated by JHipster and now we have 2 solutions:

• changing the Quarkus code to expose the same endpoints
• changing the frontend to reach the old one

If this is it, I'd rather like to change the endpoint in the backend. JHipster Quarkus is a "backend" blueprint, if we can avoid changing the frontend, it's better.

[mshima]

as I understand we changed the endpoints generated by JHipster

Yes.

If this is it, I'd rather like to change the endpoint in the backend. JHipster Quarkus is a "backend" blueprint, if we can avoid changing the frontend, it's better.

That’s it.

[avdev4j]

Great! So let's merge this one, if it's ready.

[mshima]

I don’t have commit rights.