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
Stop including snap state in controller state #876
Conversation
f8e3aa9
to
2aaf430
Compare
@@ -188,14 +193,17 @@ type StoredSnaps = Record<SnapId, Snap>; | |||
|
|||
export type SnapControllerState = { | |||
snaps: StoredSnaps; | |||
snapStates: Record<SnapId, string>; | |||
// This type needs to be defined but is always empty in practice.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then why does it need to be defined? Can we just remove it?
Also:
// This type needs to be defined but is always empty in practice.. | |
// This type needs to be defined but is always empty in practice. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We want to persist snapStates
, but not use it as controller state as that is synced with the extension UI. For us to be able to persist it, it has to be included in the SnapControllerState
027dd38
to
3bcfb49
Compare
Stops including snap state in controller state so it isn't piped to the extension UI. Instead it is stored with runtime information.