Prefer Windows Specific Path for Storing Configuration File

[catuhana]

The Problem

Currently, ferium uses ~/.config path on all platforms, which resolves to C:\Users\<User>\.config on Windows. Even though this path is used popularly for Windows apps, a Windows standard way should be preferred.

Why?

Most launchers already use platform specific paths, and it's nicer to use them.

Your Solution(s)

Use FOLDERID_RoamingAppData or FOLDERID_LocalAppData (aka %APPDATA% or %LOCALAPPDATA respectively) for Windows. We can do this in 3 ways:

1. Just append \AppData\Roaming\ to libium::HOME. This is the simplest way, but for reasons, Windows recommends using FOLDERIDs directly (which is why two the two other solutions below).
2. Use sys-traits crate's EnvCacheDir::env_cache_dir (which what Deno uses)
   • The issue with this is, this crate only supports FOLDERID_LocalAppData, which is not a bad thing, but FOLDERID_RoamingAppData is more favourable to use.
3. Use windows-rs directly
   • Since this will be a Windows only implementation, a manual simple implementation could be done, similar to cargo's code.

For testing, I've created a branch using the first solution, and everything works so far. If this is going to be considered, I can create a PR directly.

[theRookieCoder]

Yeah I've been meaning to switch to a more Windows-friendly config path for a while. I think for *NIX (macOS and Linux) ~/.config is fine, I don't think it's really necessary to use ~/Library/Application Support on macOS. As for how to get the directory, I was thinking of using dirs.

[catuhana]

Yeah I've been meaning to switch to a more Windows-friendly config path for a while. I think for *NIX (macOS and Linux) ~/.config is fine, I don't think it's really necessary to use ~/Library/Application Support on macOS. As for how to get the directory, I was thinking of using dirs.

dirs is now deprecated, which is why I didn't add it as an example. Oops, apparently it's just moved to Codeberg. My initial solution was using dirs in the first place, but I thought it was deprecated. But if we're going to use dirs, behaviour on macOS will change too, e.g. dirs::config_dir uses macOS specific ~/Library/Application Support, but I guess we can just append .config to dirs::home_dir on Unix?

[theRookieCoder]

Yes; I was planning to use ~/.config on macOS, and dirs::config_dir() for non-macOS (cfg(not(target_os = "macos))) OSs.