fix: Custom network chain id not converted to hexadecimal format#8606
Conversation
… for hexadecimal format
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
|
E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bd822468-61fa-4565-9e97-79a977309579 |
|
E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1625b535-2fc1-4a85-bc8c-fca981ac8953 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8606 +/- ##
==========================================
- Coverage 41.06% 41.05% -0.02%
==========================================
Files 1247 1247
Lines 30351 30362 +11
Branches 2963 2964 +1
==========================================
Hits 12464 12464
- Misses 17142 17153 +11
Partials 745 745 ☔ View full report in Codecov by Sentry. |
|
NicolasMassart
left a comment
There was a problem hiding this comment.
Looks good to me.


Description
This PR was merged some days before the hexadecimal chain id format, and those changes were missed when the hexadecimal chain id PR was merged.
This PR addresses the conversion to hexadecimal format and also a non handled promise when nickname is undefined when a custom network is added.
Related issues
Fixes: NA
Manual testing steps
Screenshots/Recordings
https://recordit.co/ECgXE9ZHke
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist