Skip to content
This repository has been archived by the owner on Oct 7, 2024. It is now read-only.

Ensure newly created vaults are unlocked #155

Merged
merged 1 commit into from
Nov 7, 2022

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Nov 7, 2022

A new vault should be unlocked after being created, because the password is submitted as part of creating the vault. This was accidentally broken as part of #148. A unit test has been added to ensure this doesn't happen again.

A new vault should be unlocked after being created, because the
password is submitted as part of creating the vault. This was
accidentally broken as part of #148. A unit test has been added to
ensure this doesn't happen again.
@Gudahtt Gudahtt requested a review from a team as a code owner November 7, 2022 20:48
@@ -85,7 +85,7 @@ describe('KeyringController', function () {
});

describe('createNewVaultAndKeychain', function () {
it('should set a vault on the configManager', async function () {
it('should create a new vault', async function () {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is unrelated; I just happened to notice a reference to a now-extinct "configManager" abstraction in another test. This was the last remaining reference to it.

@Gudahtt Gudahtt merged commit bc5716f into main Nov 7, 2022
@Gudahtt Gudahtt deleted the ensure-new-vault-is-unlocked branch November 7, 2022 21:29
Gudahtt added a commit that referenced this pull request Nov 7, 2022
* origin/main:
  Set password sooner to avoid redundant persistance (#154)
  Ensure newly created vaults are unlocked (#155)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants