-
-
Notifications
You must be signed in to change notification settings - Fork 35
Add note about different commands within and outside of app #51
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
What do you mean? To print a warning message? |
Yes, sorry that wasn't clear. The command behave differently in different context, so we should let the users know which context they're in. Otherwise I expect people may think "Huh? I don't see a |
@cllns Sorry for asking the question again: do you want a warning message? |
No, not a warning. For example, when outside of an existing Hanami folder: % hanami help
Commands:
hanami new APP
hanami version
Other commands available within a Hanami app:
hanami console # App REPL
hanami generate [SUBCOMMAND]
hanami install
hanami middlewares # List all the registered middlewares
hanami routes # Inspect application
hanami server |
This isn't possible. We register at the runtime two different command registries. |
Gotcha. What about something generic like % hanami help
Commands:
hanami new APP
hanami version
Other commands are available within a Hanami project's folder |
We only allow
hanami new
outside of existing Hanami projects, and only allow almost all the other commands inside a Hanami 2 project (version
is rightfully allowed in both).For example:
Something like: "There are more commands available when you're inside of an app, but we've detected that you're not in a Hanami 2 folder". We could even list them (on one line, without descriptions) too. And when inside an app something like "
hanami new
is also available when you're outside of an existing Hanami project folder."I think this could be a "good first issue" for newcomers who'd like to contribute to the Hanami 2 effort.
The text was updated successfully, but these errors were encountered: