Closed FelipeJz closed 5 months ago
Thank you for making this! Maybe can you change it so that if config.json
doesn't exist, it creates it with the defaults you have here?
I'm happy to contribute to this project, been using it every day. The file is already created in the commit with the defaults, should we check anyway?
I think so; that way if someone moves the python script elsewhere and they no longer have the config, they won't have to try and figure out the schema of the config
Right now I'm working on an audio device selector so there will be some merge conflicts with this branch; I can help resolve some of those however
I haven't tested these changes yet (just did it in the GitHub merge conflict resolver) so I'm gonna do that
I think this should be good; basically what I did was I removed the constants and referenced all config values in the config
object, that way any changes to config
done by update_config
will be propagated to the config.json
and there shouldn't be any desync
Ok so I merged this, thanks for contributing!
Always good the keep the config outside the code