We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The questions in 8.4.0 seem to be in a random order compared to 8.1.0. Here are the questions from 8.1.0:
With 8.4.0, many of the client questions are asked first, then the Cypress questions are asked at the end.
Having the questions change order between releases makes it hard to write evergreen tutorials about JHipster.
Create a project with 8.1.0 and take a screenshot of the question order. Do the same with 8.4.0 and you'll notice they're in a different order.
#26057
Make it so the questions are in the same order in v8 and beyond. You can see the order from previous releases at the links below:
8.4.0
The text was updated successfully, but these errors were encountered:
@DanielFran bounty claimed https://opencollective.com/generator-jhipster/expenses/203374.
Sorry, something went wrong.
@mshima approved
Successfully merging a pull request may close this issue.
Overview of the issue
The questions in 8.4.0 seem to be in a random order compared to 8.1.0. Here are the questions from 8.1.0:
With 8.4.0, many of the client questions are asked first, then the Cypress questions are asked at the end.
Motivation for or Use Case
Having the questions change order between releases makes it hard to write evergreen tutorials about JHipster.
Reproduce the error
Create a project with 8.1.0 and take a screenshot of the question order. Do the same with 8.4.0 and you'll notice they're in a different order.
Related issues
#26057
Suggest a Fix
Make it so the questions are in the same order in v8 and beyond. You can see the order from previous releases at the links below:
JHipster Version(s)
8.4.0
The text was updated successfully, but these errors were encountered: