-
Notifications
You must be signed in to change notification settings - Fork 14
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
Cleanup command line options & documentation #107
Comments
I can work on this, but need to clarify a bit.
It sort of makes sense that these would be somewhat different when working on workspace vs project. However for
This makes sense. We're just assuming folders with nimble files are projects? |
No, we detect the workspace and if the current working directory is a workspace then it's a workspace command. BTW since I wrote this I changed my mind: The syntax should be |
Ah ok, we just check for workspace first. I still don't really know what we do differently, but I can look at the code.
That should be easier to do. |
Many commands like
use
andpin
andrep
can work on a Workspace or an individual project. We should offerproject.use
andworkspace.use
as aliases that enforce a respective interpretation. If the qualified command syntax is not used then if the current working directory is a project the command is mapped toproject.command
and else if the working directory is a workspace it is mapped toworkspace.command
otherwise it is an error as it's not clear what was meant.The text was updated successfully, but these errors were encountered: