Skip to content

fix(vault): use singleton pattern for vaultManager#5650

Closed
dtribble wants to merge 1 commit intomasterfrom
5622a_vault_ephemera
Closed

fix(vault): use singleton pattern for vaultManager#5650
dtribble wants to merge 1 commit intomasterfrom
5622a_vault_ephemera

Conversation

@dtribble
Copy link
Copy Markdown
Member

closes: #5622

Description

Implement ephemeral state by using singleton pattern

Security Considerations

TBD

Testing Considerations

TBD

Change the ephemeral state to scoped in the makeVaultManager function
@dtribble dtribble requested a review from erights June 23, 2022 00:32
Copy link
Copy Markdown
Contributor

@Chris-Hibbert Chris-Hibbert left a comment

Choose a reason for hiding this comment

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

Hmm. That's definitely simpler, and closer to our usual JS style, but it seems further from the common pattern for our durable objects, so I'm not sure the simplicity is an advantage.

@erights
Copy link
Copy Markdown
Member

erights commented Jun 27, 2022

Note to reviewers: Hide whitespace differences before reviewing the diffs. Bigger help here than usual.

@turadg
Copy link
Copy Markdown
Member

turadg commented Jul 11, 2022

Closing because I understand @dtribble and @erights concluded we should not use the singleton pattern for vaultManager.

@turadg turadg closed this Jul 11, 2022
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.

Ephemeral state in vaultManager is incorrectly module-scope

4 participants