-
Notifications
You must be signed in to change notification settings - Fork 1
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
Unsure about wording (and hence CLI flag names) #62
Comments
The dialog is a creation process, perhaps -a could be reserved for |
Don't like the |
I like create/modify/destroy (-c -m -d) the most. "destroy" sounds more epic than "remove" or "delete", already decided with "create, so it's: create/???/destroy (-c -? -d) "edit" or "tweak" sound too amateurish and less fitting next to "create" and "destroy", so "modify" makes sense. Could also borrow from CRUD: create, read, update, delete. -u could be saved for CLI-only modification functionality (similar to -a) create/edit/delete seems to be perfect... "modify" would require "destroy", and that sounds a bit too childish and vidya |
perhaps UI-opening CLI flags should be upper-case (-C -E -D), while CLI-specific should be lower: -c -e -d |
-a should be preserved for "app" |
Related to Liquid Apps, should it be:
create/alter/destroy (-c -a -d)create/tweak/destroy (-c -t -d)when it comes down to naming buttons, classes, error messages, etc?
The text was updated successfully, but these errors were encountered: