This repository has been archived by the owner on Oct 7, 2024. It is now read-only.
feat: remove KeyringSnapControllerClient
to fix dependency problems
#241
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
Summary: This PR addresses the circular dependency issues caused by the
KeyringSnapControllerClient
class.The
KeyringSnapControllerClient
class currently relies onSnapController
. This relationship introduces an extensive range of dependencies into thekeyring-api
. Consequently, this has led to the emergence of circular dependencies within other packages that also depend onkeyring-api
.To mitigate this issue, we propose the removal of the
KeyringSnapControllerClient
class from thekeyring-api
. It's important to note that this class is exclusively utilized by theeth-snap-keyring
package, an internal component of MetaMask.