Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Prepare to support multiple wallets #34

Closed
wants to merge 1 commit into from
Closed

refactor: Prepare to support multiple wallets #34

wants to merge 1 commit into from

Conversation

kukgini
Copy link
Contributor

@kukgini kukgini commented Mar 24, 2023

Checklist

  • have run AriesFrameworkTests
  • I have run AllTests

Description

Checking the actual existance of the file may be a better approach than relying on UserDefault to determine the existence of the wallet.

In this task, I changed the way to manage master secret id. I referenced this from aries-cloudagent-python.
Master secret id is just a label given to the master secret stored in the wallet, so there is no need to create it arbitrarily.

…property.

Signed-off-by: kukgini <kukgini@gmail.com>
@kukgini
Copy link
Contributor Author

kukgini commented Mar 30, 2023

Altough this PR is titled preparing multiple wallets, My original intention was not to do so when information does not need to be disseminated. Checking wallet is exists or not is sufficient to check the wallet is really there instead of rely on other property.

@conanoc
Copy link
Contributor

conanoc commented Mar 30, 2023

That makes sense. But, I'm not sure if it's the better decision. Let me think about this later when I replace indy wallet with askar.

@conanoc conanoc closed this Mar 30, 2023
@kukgini kukgini deleted the patch-5 branch March 31, 2023 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants