fix(task): --recursive option not working

[marvinhagemeister]

We didn't handle the --recursive option properly in deno task. This PR addresses that.

Fixes #27174

[bartlomieju]

This still doesn't seem to work correctly, I have a repo like this:

- client/
   - deno.json
   - main.ts
- server/
   - deno.json
   - main.ts
- deno.json

Both client and server have a single dev task that runs deno run ./main.ts in respective packages. The root deno.json is:

{
    "workspace": [
        "./client", "./server"
    ]
}

then running:

../deno/target/debug/deno task --recursive dev
No matching task or script 'dev' found in selected packages.

or

../deno/target/debug/deno task --recursive --filter "*" dev
No matching task or script 'dev' found in selected packages.

./deno/target/debug/deno task --recursive --filter "client" dev
No matching task or script 'dev' found in selected packages.

[marvinhagemeister]

Good point, missed that case when the deno.json has no package name.

[bartlomieju]

@marvinhagemeister so now this works, but I think there's still some problems.

This looks okay, but maybe in a follow up we could improve the output to show tasks from workspace members?

../deno/target/debug/deno task
Available tasks:
  No tasks found in configuration file

This works fine:

Task dev deno run ./main.ts
Hello from client
Task dev deno run ./main.ts
Building server
Server finished

This seems to ignore the --filter argument:

../deno/target/debug/deno task --recursive --filter "client" dev
Task dev deno run ./main.ts
Hello from client
Task dev deno run ./main.ts
Building server
Server finished

../deno/target/debug/deno task --recursive --filter "./client" dev
Task dev deno run ./main.ts
Hello from client
Task dev deno run ./main.ts
Building server
Server finished

[bartlomieju]

Confirmed that it now works correctly. LGTM