One case we need to cover is backwards and forward compatiblity for the config files, i.e. a gopass user might upgrade gopass before or after gopass-jsonapi and any of these might re-write the config file to introduce incompatbile settings.
The API is implicitly loading the gopass config.
As long as it's not modified by the user the config is not upgraded, but once the user changes a config setting it might become incompatible.
One case we need to cover is backwards and forward compatiblity for the config files, i.e. a gopass user might upgrade gopass before or after gopass-jsonapi and any of these might re-write the config file to introduce incompatbile settings.
The API is implicitly loading the gopass config. As long as it's not modified by the user the config is not upgraded, but once the user changes a config setting it might become incompatible.