How to pass the args from comandline to the tasks

[harrytran998]

We have some db migration tasks. And a command-like script below. So what if I want to run the command like prisma resolve --applied "file_name" --> moon api:db.apply filename --> not worked

I already traced the docs, but it might be hard for me right now. Could anyone suggest a solution for this thing?

tasks:
  db.apply:
    preset: "server"
    command: "prisma resolve --applied"

[milesj]

@harrytran998 You just need to add -- between the moon command and the args to pass down, so it'll probably be: moon api:db.apply -- filename

[anotheri]

@milesj no, moon run app:test -- MyComponent doesn't work neither, and no matter what I try:

• command/script variations:
  • command: 'vitest run'
  • command: 'vitest'
  • script: 'pnpm test' that calls vitest run
  • script: 'pnpm test' that calls vitest;
• with/without inputs
• with/without preset: 'server' or preset: 'watcher'

And when I use script (the only way i can see actual logs of executed script, command doesn't provide such logs and i didn't find a way to see them via options) it doesn't even pass the argument into pnpm test call, see the difference between using moon task script and pnpm script call below:

and it's there when i call pnpm test with this argument directly:

Let me know if i can help with any additional testing.

[anotheri]

@milesj it seems i've found the source of my problem.

I have a conflict between .moon/tasks.yml and apps/dashboard/moon.yml like this:

# .moon/tasks.yml
test:
  command: "vitest run ."

# apps/dashboard/moon.yml
test:
  command: 'vitest run'

And whatever i've tried before (mentioned in previous comment) I put into the apps/dashboard/moon.yml assuming it'll override global tasks. But as far as i've got from reading docs a bit more it will utilize merge strategies, so i can either adjust those stragies by using something like options.merge or options.mergeArgs:

# apps/dashboard/moon.yml
test:
  command: 'vitest run'
  options:
    mergeArgs: 'replace'

Or to override global task completely I can explicitly exclude global task via inheritedTasks.

So now with command: 'vitest run' inside the project it works as expected.

But nevertheless (even if I remove the global test task completely and) if I have a project scoped task test with script: 'pnpm test' that calls vitest run it still doesn't pass an argument as i've explained above (i guess it's the same issue @airtonix mentioned before).

UPD: And by the way, is there a way to check what the merged result of a certain task look like? as shown in the end of the merge strategies section but via cli command... It might be helpful to catch/debug such issues.

[milesj]

script doesn't support passthrough args, only command. https://moonrepo.dev/docs/concepts/task#commands-vs-scripts

After all this merge stuff is resolved, does command work here?

[anotheri]

Yes, command works as expected now.
If script doesn't support passthrough args, then it's also works as expected, sorry for confusion and thanks for great work and communication!

[milesj]

Glad it's working! But yeah, inheritance can make things a bit confusing. I'm hoping to alleviate this in some way in the future.