-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix: Fix type errors in reducers #7147
Conversation
bba6da3
to
e0179d4
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #7147 +/- ##
==========================================
- Coverage 32.75% 32.34% -0.41%
==========================================
Files 1006 1006
Lines 26957 26957
Branches 2128 2128
==========================================
- Hits 8829 8719 -110
- Misses 17701 17809 +108
- Partials 427 429 +2
☔ View full report in Codecov by Sentry. |
3141bea
to
9ff03aa
Compare
All type errors in the reducers have been fixed. An error in the EngineState type was exposed during this process as well, and has also been fixed (the `PermissionControllerState` was resolving to `never` because the wrong type parameter was passed in). The `fiatOrders` unit tests used selectors quite a lot, so there was a need for a mock/initial root state shape. This was introduced in the `app/util/test` directory for use in unit tests. This initial state object represents just the minimal initial state that has been typed so far. After we migrate all reducers to TypeScript and fix their types, this state object will become increasingly complete/correct. This is a follow-up to #7110, which laid the groundwork for these type fixes but also introduced some of them accidentally.
9ff03aa
to
873980a
Compare
Kudos, SonarCloud Quality Gate passed!
|
Passing E2E smoke test run: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5617a7ae-2bc8-4bb7-aac6-c80a31aa66a9 |
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.
LGTM
Development & PR Process
release-xx
label to identify the PR slated for a upcoming release (will be used in release discussion)needs-dev-review
label when work is completedneeds-qa
: PR requires manual QA.No QA/E2E only
: PR does not require any manual QA effort. Prior to merging, ensure that you have successful end-to-end test runs in Bitrise.Spot check on release build
: PR does not require feature QA but needs non-automated verification. In the description section, provide test scenarios. Add screenshots, and or recordings of what was tested.QA Passed
label when QA has signed off (Only required if the PR was labeled withneeds-qa
)team-
(orexternal-contributor
label if your not a MetaMask employee)Description
All type errors in the reducers have been fixed. An error in the EngineState type was exposed during this process as well, and has also been fixed (the
PermissionControllerState
was resolving tonever
because the wrong type parameter was passed in).The
fiatOrders
unit tests used selectors quite a lot, so there was a need for a mock/initial root state shape. This was introduced in theapp/util/test
directory for use in unit tests. This initial state object represents just the minimal initial state that has been typed so far. After we migrate all reducers to TypeScript and fix their types, this state object will become increasingly complete/correct.Issue
This is a follow-up to #7110, which laid the groundwork for these type fixes but also introduced some of them accidentally.
Checklist