665861 - GCLI should not package any commands by default

Status: RESOLVED FIXED

(DevTools :: General, defect)

Description

[Joe Walker [:jwalker]]

Currently GCLI comes with a ``help`` command pre-installed, but not all environments will want this, and all environments will need to install their own commands, so there is little benefit in pre-installing this one.

Comment 1

[Joe Walker [:jwalker]]

Opinions?

Comment 2

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

I think it is valuable to have a place to list commands, whether or not that command is "help" or "gcli list" or "gcli help", I'm not sure which is best. I think there should be some way to see a complete list of what is available though.

Comment 3

[Joe Walker [:jwalker]]

I guess I'm suggesting that help should move to demo/commands/help. That way it's clear that embedders get a clean slate when they start.

I'm not sure what happens if someone starts GCLI with no commands, which would be more likely to happen with this change.

Comment 4

[Rob Campbell [:rc] (:robcee)]

It sounds like you might need a "base" gcli command stub that pops up some kind of "no commands registered". Or maybe ship with a single command to create new commands. Probably outside the scope of this bug though.

Comment 5

[Joe Walker [:jwalker]]

Created a branch for this in my github to keep wip. Low priority though.