Repository navigation
Task identifier shorthand notation / aliases #268
Description
In order to allow shorthand notation for tasks, consider allowing a task to be referenced by multiple values. For example, and equivalent in shell would be...
#!/usr/bin/env bash
case "$1" in
dt | do | do-thing | do-the-thing )
...
;;perhaps in a Taskfile.yml it could be...
tasks:
do-thing:
cmds:
- ...
aliases:
- dt
- do
- do-the-thingJust an idea, just putting it out there. Feel free to close whenever, etc. Thanks for your time 👍
Reacted by Constantinos Xanthopoulos and geogboe
Activity
andreynering commentedon Nov 16, 2019
Hi @aegershman,
That's kinda already possible, just more verbose:
I liked your idea though, and it's probably easy to implement.
tommyalatalo commentedon Dec 8, 2019
While you're right about this being kind of possible with your examples, it creates a very cluttered output when doing "task --list". It would be really great to have an "alias:" property to set for tasks, and probably a good way of showing the aliases in the "--list" output would be to just chain them, or have a column for aliases separately.
"chained"
alias column:
Something like the above.
andreynering commentedon Dec 16, 2019
@tommyalatalo That makes sense 👍
andreynering commentedon Dec 16, 2019
Closed by mistake, sorry.
slashsbin commentedon Feb 17, 2020
Here is another idea to achieve shortcuts automatically:
If task names are namespaced with
:(the way style guide recommends), then we could support specifying task names using the shortest unambiguous text for each part.For example lets say we have a task named
my:foo:bar, then we could run that task using the namem:f:b.This is something already supported by many other terminal commands like Symfony Console.
Also If you enter a short command that's ambiguous (i.e. there is more than one command that match), then no command will be run and some suggestions of the possible commands to choose from will be output.
aegershman commentedon Oct 14, 2021
Thanks all 👍 closing for tidyness
tommyalatalo commentedon Oct 15, 2021
What does that mean - "closing for tidyness"? Is this continued in another issue, if so, which one?
ghostsquad commentedon Feb 20, 2022
I came here to ask the same thing, then decided to open a new issue (#675), with some concrete examples of how this may be implemented, and some pitfalls.