-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate admin ui according to the flag value #12738
Generate admin ui according to the flag value #12738
Conversation
Does this mean we're going to require two apps to run one app (if you want to administer the one app)? |
Unless we use the flag I have added ;). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo
I'm not totally in favor of this, for now. The reason is the JHipster Control Center is not finished yet today, and we don't have official lead on this. So it can become a dead project, if it's not well maintained. |
This was my main issue yesterday, Maybe we should add a question, something like (Would like to administrate your application with the JHipster Control Center?(the admin ui will be not generated) y/N". Because if we add a flag like no-admin-ui I'm sure that nobody will use it :D? With this question we will be able to add the JHCC Docker compose configuration only when the answer is "yes". WDYT? |
I would say let's generate the jhcc docker compose all the time so people can try it out in any case... As for if the admin UI should be generated by default or not, I think it would be better to actually do a vote about it on the mailing list. |
910ba3d
to
3acc93d
Compare
ac6ddd7
to
659d9e5
Compare
It needs to be discussed, when admin ui is not choosen, should we keep swagger or not ?
Swagger is so important, and it would not required too much maintenance ! |
after all, I think you're right @pascalgrimaud it's not a big effort to keep that so let's revert this changes. |
if the flag is use, generate the admin ui pages Fix typo
26f9adf
to
1563578
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've quickly reviewed the JDL part.
I'll do a more thorough review for this.
...rators/client/templates/angular/src/main/webapp/app/layouts/navbar/navbar.component.html.ejs
Outdated
Show resolved
Hide resolved
...ent/templates/react/src/main/webapp/app/modules/administration/administration.reducer.ts.ejs
Outdated
Show resolved
Hide resolved
...ent/templates/react/src/main/webapp/app/modules/administration/administration.reducer.ts.ejs
Outdated
Show resolved
Hide resolved
3d7492a
to
3dd77d1
Compare
@MathieuAA I have tested many things and finally did not find the better way, except if we move to async functions. Less code, easier to read and ofc less "PROMPT" ;). I have added a commit, about that, in this PR but we can split into two different ones. This is related to this PR: #12812 What do you think @mshima @sendilkumarn ? |
8f09ef3
to
5f855ee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
2 non-blocker considerations:
- I would prefer --admin-ui instead of --with-admin-ui.
- httpsGet should be extracted into a util function instead of a generator-private member. Not the scope of this PR.
That's a much better solution @avdev4j :) |
--with-admin-ui no longer exist because we move to a prompt instead of a flag.
Not scope in this PR but let rework the function to easily extract it in the future. @mshima finally done, I think we can easily move the bootswatch functions to the prompt file to a lib. |
congrats for your hard work @avdev4j ! |
lot of work done to achieve this, so increasing the bounty, it's well deserved |
Bounty claimed https://opencollective.com/generator-jhipster/expenses/27873 |
@avdev4j : approved |
Add a --with-admin-ui flag to generate the admin ui pages. By default, those pages are not generated and the user should use the JHipster Control Center application.
EDIT: add prompt instead
#12167
#12090
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding
skip-ci
label, you can still see CI build result at your branch.