[CLI] Do not prompt for Application Class name

[virkt25]

Description / Steps to reproduce / Feature proposal

From #1206

Why do I need to create a class?

Related Notes:

Refers to the CLI prompting for Application Class Name. No description of what that Application class refers to.

---

We already prompt the user for a Project name and then prompt for an Application class name.

Acceptance Criteria

• Remove prompt for Class Name (Use the default we generate) -- this will prevent users from having to enter the it again / get confused about what the Application class name is.
  • Might be good to have a message stating the name of the class that we generated.

See Reporting Issues for more tips on writing good issues

[raymondfeng]

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 Application is not clear, we can add a link or make it more descriptive in the CLI.

[bajtos]

+1 for making the CLI prompts more descriptive, so that users understand why we are asking them about application class name.

[jannyHou]

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.

[shimks]

^^^ 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 (--applicationClassName=CustomNameApplication).

I'm ok with the short and concise description during the prompt though.