app-dirs-rs
app-dirs-rs copied to clipboard
andybarron
Put your Rust app's data in the right place on every platform
PR to make `AppInfo` a trait and have different structures with different ownership semantics for it. Resolves issue #19 I still think there should be some way to use `Cow`...
Often command line tools on macOS use unix locations for dotfiles, I essentially never look in ~/Library/ to configure my tools. Because of this, I've avoided this crate for my...
The [`AppInfo`][appinfo] struct stores the `&'static str` type, which fails miserably if any of the fields are borrowed from an owned `String`. It should be changed to use an explicit...
[`std::path::Path`][std_path] is the standard library's way of storing immutably borrowed paths. [`sanitized`][fn_sanitized], [`app_dir`][fn_app_dir] and [`get_app_dir`][fn_get_app_dir], however, use normal borrowed strings and try to enforce path separators via documentation, which is...
- `get_app_file` would be identical to `get_app_dir`. - `app_file` would: - Call `create_dir_all` on the path's parent. - Call `OpenOptions::new().create(true).append(true).open` on the full path. - Return the full path. -...
The documentation for `get_app_dir` claims that it "[r]eturns (but **does not create**)" the path. However, its implementation calls `get_root` which does in fact create the path anyway. The other getters...
Hi, there are some use cases (for example using clap and app_dirs in the same app) when you'd want to create your object which you could pass to app_dirs functions....
Metadata
Owner
Metadata
Put your Rust app's data in the right place on every platform