On 06/02/2015 02:18 PM, John Florian wrote:
> Subject: Koji 2.0 planning
That sounds great! One thing I'd love to see (still being quite new
to koji) is improved consistency in the CLI. It's not bad now, but
being less than perfect requires that I almost always seek help.
For example, for every NOUN provide: add-NOUN, edit-NOUN, list-NOUN
(and/or show-NOUN), remove-NOUN. If I were implementing this, I
would subclass all from base classes and in cases where something
cannot be permitted, e.g., removal for database
constraints/integrity, have the base class provide a default behavior
saying something like "This is not possible due; not because of
authorization but by design." Such extra commands might seem like
clutter, but they also would help in being somewhat self-documenting.
"koji help" could be shortened drastically by mentioning something
like:
Maintenance Commands: {add,edit,list,show,remove}-NOUN where NOUN can
be any of: group, pkg, user....
Good idea. We could certainly use more consistency there. Similarly with
the api calls.
Just my $0.02. Regardless, I look forward to the progress.