`XDG_CONFIG_HOME/task` config should not be a hidden file

[pd93]

Could I suggest that we strip the initial dot in the taskcfg.yml that lives on $XDG_CONFIG_HOME/task?

Having a hidden file there only makes it harder to see it, and it is a common pattern. See for instance git: ~/.gitconfig vs. ~/.config/git/config.

Originally posted by @panchoh in #2380 (comment)

[pd93]

CC @vmaerten I think this is a good point.

@panchoh, do you have thoughts on a naming convention? You mentioned that git drops the git prefix in their config file as well as the . prefix, but $XDG_CONFIG_HOME/task/rc.yml feels a bit odd to me?

Options (assuming .yml for all, but we would support both .yml and .yaml to be consistent with Taskfiles:

• $XDG_CONFIG_HOME/task/.taskrc.yml <-- current
• $XDG_CONFIG_HOME/task/taskrc.yml
• $XDG_CONFIG_HOME/task/rc.yml
• $XDG_CONFIG_HOME/task/config.yml

[panchoh]

(Thanks for opening up this one, @pd93!)

You summed it up pretty well, I personally would go for config.{yml,yaml}, since now the context is clear (provided by the path, that is). But anyone will do.

Ripgrep uses ripgreprc, for instance.

[vmaerten]

I agree!
$XDG_CONFIG_HOME/task/config.yml is good but we will loose JSON schema or maybe we can adapt the path in https://github.com/SchemaStore/schemastore to also match this path

[andreynering]

I agree with allowing the file to be without the leading dot inside $HOME/.config/task/. We could maybe also allow taskrc.yaml without the dot on the repository, for consistency.

Regarding the name, it's not a strong opinion, but I think I would keep .taskrc.yml and taskrc.yml as options (and not config.yml) for consistency and clarity. In theory even the code will be simpler because we can maintain a single list of possible names instead of two.

And of course, both .yml and .yaml should be supported.

[panchoh]

I was a bit confused about the scope of the taskrc file; I thought it would be a full-fledged Taskfile, so I was going to suggest naming it as such. But after reviewing the doc, I see now that the taskrc file is as advertised: a proper rc file.
So, I’ll say that I’m completely satisfied by calling it taskrc (plus suffixes, that is).

Thanks again!