microsoft / microsoft/go-sqlcmd
XDG Base Directory Specification
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
Like briefly mentioned in #329, the current config path is a custom arbitrary one: ~/.sqlcmd/sqlconfig as explained in the documentation.
However having ~2000 "dotfiles" and "dotfolders" in $HOME is a bit anoying and messy.
That is why I suggest implementing a XDG compliant config deployment.
- Specs: XDG Base Directory Specification
- Env vars: XDG_CONFIG_HOME (default to $HOME/.config for users) and XDG_CONFIG_DIRS (default to /etc/xdg for system)
- Go libs: go-appdir (archived) - configdir (abandoned) - kyoh86/xdg (archived) - adrg/xdg (up to date)
The idea would be to have ~/.config/sqlcmd/sqlcmd instead of the legacy ~/.sqlcmd/sqlconfig (that could be kept as fallback for retro-compatibility).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the code that reads the legacy ~/.sqlcmd/sqlconfig path, then review the XDG Base Directory Specification and the proposed XDG_CONFIG_HOME and XDG_CONFIG_DIRS behavior. Done means using ~/.config/sqlcmd/sqlcmd by default while retaining the legacy path as a fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100