-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[CLI] Do not prompt for Application Class name #1297
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
Comments
I think the proposal is against our intention - we want to have reasonable defaults based on conventions for the code generation but we also want to allow users to confirm/customize. If the concept of |
+1 for making the CLI prompts more descriptive, so that users understand why we are asking them about application class name. |
I also tend to omit the customizing step of the app class name, don't feel people often have the need to rename it...we can either make the prompt message more descriptive, or remove it and add a short document says we allow the customization. |
^^^ I'm for removing the prompt for the application class name as well. In my opinion, the users that do want to customize their application class name should be able to set up a flag ( I'm ok with the short and concise description during the prompt though. |
Rejecting for estimation. More feedback wanted on what to do with the issue. Follow up spike is needed to hash out what are the potential UX we want to provide. |
I'd like to propose to move this out of DP3. IMHO, this is a minor issue compared to other UX issues we're having, e.g. CLI for models/datasource/relations. |
+1, I have changed the labels accordingly. |
related to #1340 |
@virkt25 , we now have the |
Yep. |
Description / Steps to reproduce / Feature proposal
From #1206
Related Notes:
We already prompt the user for a
Project name
and then prompt for anApplication class name
.Acceptance Criteria
Application class name
is.See Reporting Issues for more tips on writing good issues
The text was updated successfully, but these errors were encountered: