Currently the only way to configure seniore is managing the existing JSON file that contains all keys. This file is well documented, but forcing users to change it manually is not the best we can do.
The idea is to update this file format to a more simple key-value file used by tools like git (yep, I am that original):
After that restructuring, we can add a new config command that allows modifying the configuration without touching the actual file. As a result, we can avoid such a bad experience like
Currently the only way to configure seniore is managing the existing JSON file that contains all keys. This file is well documented, but forcing users to change it manually is not the best we can do.
The idea is to update this file format to a more simple key-value file used by tools like
git(yep, I am that original):After that restructuring, we can add a new
configcommand that allows modifying the configuration without touching the actual file. As a result, we can avoid such a bad experience like