Fix recoveryCode
, privateKey
, privateKeyPath
options usage in PolykeyAgentOptions
#601
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR builds on #600 by implementing types that were added in the last PR, these include
These types are a part of
src/keys/KeyRing
which is responsible for setting up the KeyRing, which is crucial in setting up the root key pair.These types are implemented in keyRing as so:
In
PolykeyAgent
, the start function ofKeyRing
is called in thestart
function ofPolykeyAgent
.Therefore, the further part of this PR is to pass the types in the start function of
PolykeyAgent
, which would be something like this:Also, a thing to note here is that, recoverCode, privateKey and privateKeyPath can be independently supplied, which is ensured by:
in KeyRing start.
Consequently, they are similarly implemented in PolykeyAgent types
Tasks
Final checklist