deno task: recursive task always fuzzy matches and runs unwanted tasks in child projects

[WilcoKruijer]

When working with workspaces, running deno task -r <task> will fuzzy match for the name of the task. This is unexpected and inconvenient when working with a common NodeJS script naming convention where we have a task named lint for linting once, and a task named lint:watch for lint & watching. Because of the fuzzy match, deno task -r lint would start watchers and not actually lint all sub-projects.

To reproduce, run the following:

cd /tmp && \
mkdir -p deno-workspace-repro/app1 && \
cd deno-workspace-repro/app1 && \
deno init && \
cd ..  && \
echo '{ "workspace": ["./app1"] }' > deno.json

Now observe that running deno task -r d will start the dev task.

Version: Deno 2.1.4

[bartlomieju]

Same problem as in #27370