External commands should be registered before custom commands #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Right now, the dynamic/custom commands are registered in the
TaskRunner
constructor. The external commands, provided by 3rd party, are registered afterTaskRunner
has been constructed, in./bin/run
:For this reason a custom command cannot add an external command as a task because at that moment the external command is not yet registered.
Solution
Call
::registerExternalCommands()
from theTaskRunner
constructor, just before calling::registerDynamicCommands()
.