Melkeydev / go-blueprint

Go-blueprint allows users to spin up a quick Go project using a popular framework
https://docs.go-blueprint.dev/
MIT License
5.9k stars 333 forks source link

fix: Missing argument [command] in non-interactive command tip #123

Closed Yoquec closed 1 year ago

Yoquec commented 1 year ago

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

Problem/Feature

When creating a new project without specifying any arguments, the non-interactive command tip showed at the end was missing the sub command (create, help, etc).

For example, before:

$ go-blueprint create
 ____  _                       _       _
|  _ \| |                     (_)     | |
| |_) | |_   _  ___ _ __  _ __ _ _ __ | |_
|  _ <| | | | |/ _ \ '_ \| '__| | '_ \| __|
| |_) | | |_| |  __/ |_) | |  | | | | | |_
|____/|_|\__,_|\___| .__/|_|  |_|_| |_|\__|
                   | |
                   |_|

 What is the name of your project?

...

 Tip: Repeat the equivalent Blueprint with the following non-interactive command:
 • go-blueprint --name test --framework echo --driver none

When repeating the command go-blueprint --name test --framework echo --driver none it wouldn't create the project structure, as the word create was missing.

Now, the output is:

 Tip: Repeat the equivalent Blueprint with the following non-interactive command:
 • go-blueprint create --name test --framework echo --driver none

Description of Changes:

Checklist