The change passes the displayName of a vault to a keychain backend, namely the storePassphrase and deletePassphrase methods.
Having the displayName enables the backend to process and store it.
The change should be non-disruptive, which means that backends that have no interest in the new parameter displayName do not need to be changed due to this API change.
Cryptomator itself needs a change too, in order to make use of this change. Another PR takes care of that.
The change passes the
displayNameof a vault to a keychain backend, namely thestorePassphraseanddeletePassphrasemethods.Having the
displayNameenables the backend to process and store it.The change should be non-disruptive, which means that backends that have no interest in the new parameter
displayNamedo not need to be changed due to this API change.Cryptomator itself needs a change too, in order to make use of this change. Another PR takes care of that.