Closed exastone closed 1 month ago
convention for dev tools config files on macOS is same as linux i.e. $HOME/.config/.
$HOME/.config/
use of os.UserConfigDir() yields "$HOME/Library/Application Support" see: https://github.com/xo/usql/blob/8519ebd9888c5120eb9e757e3a37914c7d04157e/env/types.go#L703
os.UserConfigDir()
i believe the switch-case in buildConfigDir() is redundant as this copies functionality of os.UserConfigDir() see: https://github.com/xo/usql/blob/master/env/types.go#L706
buildConfigDir()
Happy to submit a PR if i can get an idea of what is the desired outcome here. if config dir isn't found what is the desired action. also, realpath is used in buildConfigDir() but i don't see an obvious purpose.
Open to discuss this,
This was done on purpose so that the command help would have both the expanded path and the relevant home path. We're always open to well written PRs.
convention for dev tools config files on macOS is same as linux i.e.
$HOME/.config/
.use of
os.UserConfigDir()
yields "$HOME/Library/Application Support" see: https://github.com/xo/usql/blob/8519ebd9888c5120eb9e757e3a37914c7d04157e/env/types.go#L703i believe the switch-case in
buildConfigDir()
is redundant as this copies functionality ofos.UserConfigDir()
see: https://github.com/xo/usql/blob/master/env/types.go#L706Happy to submit a PR if i can get an idea of what is the desired outcome here. if config dir isn't found what is the desired action. also, realpath is used in
buildConfigDir()
but i don't see an obvious purpose.Open to discuss this,