-
Notifications
You must be signed in to change notification settings - Fork 63
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
feat!: Restructure custom-object commands to match design guidelines #1261
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments/questions, nothing really blocking though
}, | ||
]); | ||
return input; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we really just need to upgrade to the new inquirer haha
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah haha. The current version we are on its pretty unintuitive
…ture-custom-object-commands
…ture-custom-object-commands
Description and Context
hs custom-object
--help
flag because they don't do anythinghs custom-objects
custom
alias (too generic)hs custom-object schema
hs custom-object schema list
--version
flag because it's unnecessaryhs custom-object schema fetch
--version
flag because it's unnecessaryhs custom-object schema fetch-all
hs custom-object schema create
--version
flag because it's unnecessarypath
and should be moved to be a flag instead of a positionalhs custom-object schema update
path
and should be moved to be a flag instead of a positionalhs custom-object schema delete
--version
flag because it's unnecessary--force
flag to bypass the prompths custom-object create
path
and should be moved to be a flag instead of a positional--version
flag because it's unnecessary