I think keeping things consistent with existing code is important as it
means that the current code remains in a "releaseable" state - i.e.
there is nothing "wrong" with it and it doesn't put any assertions on
what "should" happen in the future, or indeed "when" that should happen.

That said, I think I would prefer to merge this PR and then do another
PR which prefixes all the commands with "node" or "type" or "workspace"
and that fixes the class names also.

On Wed, May 01, 2013 at 12:05:49AM -0700, David Buchmann wrote:
>    In Command/NodeMoveCommand.php:
> 
>  > +use Symfony\Component\Console\Output\OutputInterface;
>  > +
>  > +/**
>  > + * @author Daniel Leech <daniel@dantleech.com>
>  > + */
>  > +class NodeMoveCommand extends BaseNodeMoveCommand
>  > +{
>  > +    /**
>  > +     * Configures the current command.
>  > +     */
>  > +    protected function configure()
>  > +    {
>  > +        parent::configure();
>  > +
>  > +        $this
>  > +            ->setName('doctrine:phpcr:move')
> 
>    but you add something new here, so i don't see the point of adding it
>    wrong and then do a PR to fix it :-) nothing will fail, it will just be
>    inconsistent until we fixed phpcr-utils.
>    its not the same repository as phpcr-utils anyways.
> 
>    —
>    Reply to this email directly or [1]view it on GitHub.
> 
> References
> 
>    Visible links
>    1. https://github.com/doctrine/DoctrinePHPCRBundle/pull/56/files#r4033363