-
Notifications
You must be signed in to change notification settings - Fork 975
Split PaymentsTab into its own component #6529
Conversation
55fc7e2
to
ca440fc
Compare
ca440fc
to
b220900
Compare
I tried running this locally (macOS) via
When I scrolled up to where the test was executed, you can see the additional errors logged via stdout:
Is there something I missed? |
f746c78
to
a7e6e75
Compare
@bsclifton sorry! was messing around with them late last night and made a breaking change. Should be good now although two of the (unrelated) preferencesTest.js tests are broken in master. I'll follow up on those separately with @bbondy. |
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.
@jkup AFAIU this PR only cover tests for payments, correct? Would the split of payments tab component be a follow-up, then?
Current tests LGTM ++
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.
Tested it out, everything works as expected (I updated the original post to show a way to only run these ones). Great job! 😄
@cezaraugusto this PR is also breaking the payments tab out from |
If this looks good to you (either @cezaraugusto or @bbondy), please approve using GitHub and then mark with the ready-to-merge label 😄 |
ok sorry, GitHub grouped LGTM |
Please make sure that there are several PRs which will be possibly conflicted if this is merged first. Could I remove the ready-for-merge label for now, so that this PR will not be merged first? thanks |
65c7753
to
238cfd3
Compare
Rebasing this now... should be a great cleanup 😄 |
a7e6e75
to
7aac987
Compare
Gonna watch CI on this one; should be good to merge though! 😄 |
Reran failing tests locally; a few unrelated tests seem to be perma-failing I believe it's safe to merge this since the ledger tests are passing and the failing tests are not impacted by these code changes |
7aac987
to
522f0e3
Compare
Preferences tests (redo of #6529)
re-assigned 0.13.1 milestone after merge was redone properly |
git rebase -i
to squash commits (if needed).This ticket both splits PaymentsTab out into its own component and adds automated tests for its functionality.
Fix #6528, fix #5887
@bsclifton I'm not thrilled with my fakeSetting API, can you help me make it a little more scalable? Maybe in another ticket? Eventually I assume we'll need more than just true for all or false for all which is all mine can handle!
Auditors @bsclifton @bbondy @cezaraugusto please let me know what you think!
Test Plan:
npm run unittest -- --grep="Preferences component"
Ready for people to take a look at this! You can change line 15 on paymentsTabTest.js to be describe.only and then with watch-all running you can just run
npm run unittest
.#6456 #6455 #6422