New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow operating system config location standards #1276
Comments
This sounds like a very good idea! 👍 We only need to make sure to make it backwards compatible. |
Great to see activity again! Guess you were really busy with v2. :) Maybe of interest for you, my two cents since I've done this for other projects like electron-download, js-v8flags, greenkeeper and node-gyp. Easiest is making a major breaking change but for user facing config this is a no-go, the now cli falls in this category. There is the option to migrate the config but this can be unexpected behaviour for the user. So the most straightforward way that I would recommend is first reading from the 'old' location and falling back to the new location, documenting this and encouraging users to use the new location. Code-wise something like this:
|
Just to add to @Siilwyn's comments (which I agree with). You should also begin writing by default to the new location for all new users. That's key. Stop writing to home entirely for new users (unless explicitly asked to do so). So, in other words, keep looking in the old location first, but stop writing to the old location if nothing exists there already. |
Closed by #1909. |
It would be great if this module followed the XDG Base Directory Specification. Instead of placing the config directory
.now
in the home directory it should be placed in the OS specific appropriate directory. Getting the correct directory is easy with a module like env-paths. This, among other things, allows a user to specify a directory in which they want all applications to look for their user configurable setting files and keep their home directory clean.For more context, this long standing issue on Atom contains a lot of replies with people wanting Atom to follow the standards for various reasons.
The text was updated successfully, but these errors were encountered: