Repository navigation
Conditional inclusions #2880
Description
Activity
Combine "conditional inclusions" with "optional inclusions" and see if you can find a way that works.
version: '3' var: DOCKER: sh: "docker" # somehow like this - if .dockerenv then echo "docker" includes: build: ./Taskfile_{{DOCKER}}.yml optional: trueThe design tension here is that includes are resolved during taskfile loading (in
taskfile/reader.go::include()), while preconditions are evaluated during task execution. So naively portingpreconditions:to theincludes:block means evaluating shell commands at parse time — which changes the loading model and introduces ordering issues (e.g., if the precondition depends on a task you haven't run yet).@trulede's template-variable +
optional: trueapproach works for cases where the decision can be reduced to a variable. The currentvars:system supportssh:for dynamic variables, so you could express the devcontainer check as:vars: IN_DOCKER: sh: '[ -f /.dockerenv ] && echo "docker" || true' includes: devcontainer: taskfile: ./Taskfile_{{.IN_DOCKER}}.yml optional: true
But this is fragile — when
IN_DOCKERis empty, the include resolves to./Taskfile_.ymlwhich likely doesn't exist but could accidentally match a real file.A cleaner design would be adding a
whenfield to theIncludestruct that takes a Go template expression evaluated against the existing vars/globals, evaluated during include resolution (not task execution). This keeps the evaluation at load time but uses the template engine rather than shell, avoiding the need to spawn subprocesses during loading:includes: devcontainer: taskfile: ./Taskfile_devcontainer.yml optional: true when: '{{.IN_DOCKER}} != ""'
The
whenfield would be a string template expression, evaluated inreader.go::include()before the goroutine spawns. If the expression evaluates to"false"or an empty string, the include is skipped (same asoptional: truewith missing file). This is consistent with how Taskfile already uses Go templates for interpolation and avoids the architectural complexity of deferred include resolution.The type change would be minimal: add
When stringtoast.Include, addwhento the YAML decoding inast.Include.UnmarshalYAML, and add a conditional skip inreader.gojust before the goroutine spawns.Happy to sketch a PR if this direction makes sense.
Description
There is a nice little feature that you support currently is preconditions.
e.g.
It would be cool to apply this to an include. For example, so I can how some tasks apply only to the task when running inside a devcontainer. Or alternatively outside a devcontainer.
Or apply to whatever precondition you define.
e.g.
Unless you have a better alternative idea or is there something I can do to make this work regardless?
And why would I want to do this you ask?
Well in situations like these:
I'd like to hide the "dev" option or make it not even available or even show up in the help if the precondition is false.