Best practices for handling multiple dependencies that conform to the same protocol?

[BrentMifsud]

Here's an example:

In our app, we have a protocol called KeyValueStore

UserDefaults conforms to it, and is the default implementation in most cases throughout our app.

But we do have some other implementations of it. For example, we have an implementation that is scoped to the user's currently active account. So if the user switches accounts, they aren't seeing values from their other account.

I see two potential options:

Option 1: multiple dependency keys

you could make a UserDefaultsKeyValueStoreDependencyKey and also a AccountScopedKeyValueStoreDependencyKey

struct DefaultsKeyValueStoreDependencyKey: DependencyKey {
    static var liveValue: any KeyValueStore = UserDefaults.standard
}

struct AccountScopedKeyValueStoreDependencyKey: DependencyKey {
    static var liveValue: any KeyValueStore = AccountScopedKeyValueStore()
}

Option 2: single dependency key, but replace via withDependencies

you would make a single KeyValueStoreDependencyKey

and then when you need the account scoped value store, you would do:

withDependencies {
    $0.keyValueStore = AccountScopedKeyValueStore()
} operation: {
    MyClass()
}

Wondering what people's thoughts on a best practice for this? Especially since I essentially want these both to have a single instance throughout the code base.