feat: allow wildcards to match multiple tasks #2121
Merged
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.
Fixes #2072
As discussed in #2072 and #1489 (comment), this PR allows calls to match multiple tasks when using wildcards. For example, given the following Taskfile:
Currently, if you run
task start:foo:1
, you will get an error:However, after this change you will see
and if you run
task start:foo
, you will getWorth noting that the order is important. If you swap the tasks around, then you will be unable to call
start:*:*
. This is because if multiple tasks match, Task will use the task that is listed first in the Taskfile. In general, it is recommended to write more specific tasks (i.e. ones with more parameters) first.