Problem
gws subcommand names mirror the underlying API method names, which use camelCase (e.g. getProfile, calendarList). CLI users naturally try kebab-case equivalents (get-profile, calendar-list), which fail — though the error does include a hint about the correct name.
Example
gws gmail users get-profile --params '{"userId":"me"}'
# error: unrecognized subcommand 'get-profile'
# tip: a similar subcommand exists: 'getProfile'
Proposed improvement
Add kebab-case aliases for all camelCase subcommands, or normalize subcommand lookup to accept both forms. This follows the Unix convention (where kubectl get-pod and similar patterns are common) and significantly reduces first-use friction for developers who haven't memorized the exact casing.
Problem
gwssubcommand names mirror the underlying API method names, which use camelCase (e.g.getProfile,calendarList). CLI users naturally try kebab-case equivalents (get-profile,calendar-list), which fail — though the error does include a hint about the correct name.Example
Proposed improvement
Add kebab-case aliases for all camelCase subcommands, or normalize subcommand lookup to accept both forms. This follows the Unix convention (where
kubectl get-podand similar patterns are common) and significantly reduces first-use friction for developers who haven't memorized the exact casing.