Problem/Motivation
This functionality currently exists, but is hard to find and requires the use of a non-intuitive flag.
Rather than overload the queue-content-single-item command with `--force` thereby breaking the convention of commands for queuing and commands for migrating, create a command that makes it obvious in using it, that you will queue and migrate at the same time.
Steps to reproduce
N/A
Proposed resolution
Create a separate command that does queueContentSingleItem() called queue&Migrate and avoid the need for the “—force” flag.
Remaining tasks
Create the new command and test it.
User interface changes
Probably none for now.
API changes
N/A
Data model changes
N/A
Comments
Comment #3
adamzimmermann commentedComment #4
markdorisonLGTM!
Comment #5
apotek commentedThis looks like a great refactoring of the existing command, and addition of the new one. While I guess one wouldn't need to support the disable duplicate checking flag for a single item migration, it can't hurt and does keep the interface to this command consistent with other migration commands.
This should also allow for wiring up a UI element in the content editing form, for remigrating the item currently being looked at.
Nice work. I keep wishing we could make these command names shorter, and was going to suggest removing the "content" part (so that content becomes the default, and keyword can stand on its own), but I think what we've got here is good.
Nice work.
Comment #7
adamzimmermann commented