if we put all admin commands under the tea admin namespace, do we need a ADMIN category? the admin command will be the only one in this category.. though I agree it shouldn't be in any of the existing categories.. hm.
maybe rename it to a more generic MISC?
if we put all admin commands under the `tea admin` namespace, do we need a `ADMIN` category? the admin command will be the only one in this category.. though I agree it shouldn't be in any of the existing categories.. hm.
maybe rename it to a more generic `MISC`?
noerw
Action: func(cmd *cli.Context) error {// TODO: this is just a stub for all admin actions// there is no default admin actionreturn nilreturn cli.ShowCommandHelp(cmd, "")would be a good default behaviour i thinkreturn err}fields, err := userFieldsFlag.GetValues(cmd)if you put that before the request, flag validation will fail faster (i.e. before waiting for the request)
)var cmdAdminUsers = cli.Command{Name: "user",userscatSetup = "SETUP"catEntities = "ENTITIES"catHelpers = "HELPERS"catAdmin = "ADMIN"if we put all admin commands under the
tea adminnamespace, do we need aADMINcategory? the admin command will be the only one in this category.. though I agree it shouldn't be in any of the existing categories.. hm.maybe rename it to a more generic
MISC?How about add statistics for users and search by name and email keyword? It seems list users is not very useful.
Reviewers