Display boolean values when signing typed data #2142
Merged
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
This PR applies the same fix as the browser extension (MetaMask/metamask-extension#4639)
The issue is that boolean values have special meaning in JSX and do not render their string representation. The solution is to simply
toString
the values to be displayed. Note that
is used instead of${...}
toString
directly to avoid any error from null or undefined values.Unfortunately, I was not able to build the MetaMask mobile app to verify my change works. I followed the steps for building on Android but ran into a few issues that I couldn't get past (specifically, I get an error building
react-native-aes-crypto
:error: method pbkdf2Sync(String,String,Integer,Integer) is already defined in class RCTAes
).That being said, I was able to test my assumption that rendering
boolean
s is an issue using the playground on the React Native dev site.Issue
Resolves #2141