[ditz-talk] [PATCH] Allow ditz claim abcd oprah
wmorgan-ditz at masanjin.net
Wed Nov 26 17:53:01 EST 2008
Reformatted excerpts from Thomas Nichols's message of 2008-11-10:
> Something like a 'ditz nick' command with add/remove? And these would
> get added to the devs (better renamed as nicks or aliases) hash in
That sounds good. In general doing anything to project.yaml, or anything
except adding a new file to .ditz/, is asking for irritating conflicts
at merge time, but the usage case for this plugin is for more
centralized development, so it's not as big of a deal.
> Nice. So if the nick is defined, use its expansion, otherwise use the
> literal string?
> ? Do we: check for a valid release name, if not found check for a
> valid nick/alias? Do we say it *must* be a release, so you cannot
> search for all claimed tickets for a developer? Do we add a new
> switch so we can
> * ditz claimed --claimer oprah
> I also smell feature creep here -- what about 'ditz mine', should that
> take a --claimer switch, or perhaps an optional positional param? What
> about 'ditz add', to automatically claim a ticket as it's being
> entered? &c. &c.
Yeah, we have to strike a balance. Currently there's no way for a plugin
to add options to an existing command (only to replace it entirely), so
the 'ditz add' case is solved for us. :)
I'm fine with either approach for 'ditz claimed'. Probably the most
friendly to the user would be for it to accept both nicknames and
releases, and to error out if it's ambiguous. That's kind of how the
issue hash name works: if you specify a hash prefix that's ambiguous, it
just yells at you at dies.
William <wmorgan-ditz at masanjin.net>
More information about the ditz-talk