Concatenation of global task arguments

[d-corler]

If I understand correctly this documentation we can only merge a global task with a local definition of a project

📁 /
├── 📁 .moon
│   └── 📁 tasks
│       └── tag-vite.yml
└── 📁 projects
    └── 📁 example
        └── moon.yaml

I define the command in a global task

# .moon/tasks/tag-vite.yml
tasks:
  cleanup:
    command:
      - pnpm
      - exec
      - rimraf
    local: true

I import the global task with the tag and extend it with an argument

# projects/example/moon.yml
tags: [vite]

tasks:
  cleanup:
    args:
      - dist

---

🤔 What can be the strategy if I want to "build" a command trough multiple global tasks definition ?

For example, I want to flavour my rimraf command to suit different paradigms using tags

📁 /
├── 📁 .moon
│   └── tasks.yml
│   └── 📁 tasks
│       ├── tag-vite.yml
│       └── tag-vitest.yml
└── 📁 projects
    └── 📁 example
        └── moon.yaml

The general task, to define the beginning of the command

# .moon/tasks.yml
tasks:
  cleanup:
    command:
      - pnpm
      - exec
      - rimraf
    local: true

The vite extension of the command

# .moon/tasks/tag-vite.yml
tasks:
  cleanup:
    args:
      - dist

The vitest extension of the command

# .moon/tasks/tag-vitest.yml
tasks:
  cleanup:
    args:
      - coverage

Usage of tags in the project manifest

Tags	cleanup command composition
vite	pnpm exec rimraf dist
vitest	pnpm exec rimraf coverage
vite + vitest	pnpm exec rimraf dist coverage

It's currently possible or do I need to fine tune each arguments at project level ?

[milesj]

Right now this isn't possible because all global (non-project) tasks are shallow merged into a global hash map, then inherited by the project. This basically means that each cleanup task would overwrite the previous one completely, it's basically a map.insert(key, value).

This is the same request as this issue: #1840