Constrain BaseController state to be valid JSON #366
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
|
The BaseController state is now constrained to valid JSON. Anything that can't be serialized (e.g. functions) or gets mutated during serialization (e.g. `undefined` gets converted to `null`) is disallowed. This should prevent an entire class of bugs resulting from unexpected changes when serializing state as JSON. For example, we serialize state when sending it over `postMessage`, and when persisting the state.
Gudahtt
force-pushed
the
constrain-base-controller-state-to-be-json
branch
from
7862dc2 to
91e9715
Compare
Member
Author
|
Note that I haven't added any test cases for this type, as testing that types work properly can be a bit challenging. But the comment I got this type from did include a TypeScript playground link will a comprehensive set of tests. I had intended to look into something like |
Contributor
|
that type is ingenious. |
MajorLift
pushed a commit
that referenced
this pull request
Oct 11, 2023
The BaseController state is now constrained to valid JSON. Anything that can't be serialized (e.g. functions) or gets mutated during serialization (e.g. `undefined` gets converted to `null`) is disallowed. This should prevent an entire class of bugs resulting from unexpected changes when serializing state as JSON. For example, we serialize state when sending it over `postMessage`, and when persisting the state.
MajorLift
pushed a commit
that referenced
this pull request
Oct 11, 2023
The BaseController state is now constrained to valid JSON. Anything that can't be serialized (e.g. functions) or gets mutated during serialization (e.g. `undefined` gets converted to `null`) is disallowed. This should prevent an entire class of bugs resulting from unexpected changes when serializing state as JSON. For example, we serialize state when sending it over `postMessage`, and when persisting the state.
Mrtenz
pushed a commit
that referenced
this pull request
Oct 16, 2025
…ner@v1 (#366) ## Summary This pull request changes the Security Code Scanner reference from `metamask/security-code-scanner@main` to `metamask/action-security-code-scanner@v1`. This change aligns with our versioned workflow approach and MetaMask naming conventions. This is a non-breaking change that only affects the action reference name. If you have any questions, please reach out to the MetaMask Security team.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The BaseController state is now constrained to valid JSON. Anything that can't be serialized (e.g. functions) or gets mutated during
serialization (e.g.
undefinedgets converted tonull) is disallowed.This should prevent an entire class of bugs resulting from unexpected changes when serializing state as JSON. For example, we serialize state when sending it over
postMessage, and when persisting the state.