We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Keep user configurations in some kind of config file that's loaded at startup
Probably makes sense to keep this in a consistent configuration directory (e.g. ~/.config on Linux - see dirs or directories)
~/.config
For now it might make sense to just put it in the project root since that might be easier for testing/development process, but I'm not sure yet.
EDIT: just occurred to me that perhaps this is a bad idea as we don't particularly want the in-use settings file to be under source control
Maybe check ./ first before checking config file? Or, check ./ with --features dev or some other flag? Or on cfg!(dbg_assertions)
./
--features dev
cfg!(dbg_assertions)
Eventually this file will be editable in-game via settings menu.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Keep user configurations in some kind of config file that's loaded at startup
Probably makes sense to keep this in a consistent configuration directory (e.g.
~/.config
on Linux - see dirs or directories)For now it might make sense to just put it in the project root since that might be easier for testing/development process, but I'm not sure yet.
Maybe check
./
first before checking config file? Or, check./
with--features dev
or some other flag? Or oncfg!(dbg_assertions)
Eventually this file will be editable in-game via settings menu.
The text was updated successfully, but these errors were encountered: