-
Notifications
You must be signed in to change notification settings - Fork 68
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
Moving hook initialisation functions out of constructors #7355
Conversation
…sts and ruleset accordingly.
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.42 MB ℹ️ View Unchanged
|
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.
Looks good, but I haven't smoke-tested.
Compare the changeset for the WCPay_Account class - I slightly altered the order of actions/filters to order them more logically, but we should double check to make sure nothing went wrong.
This also appears fine.
It's a from me once we smoke test
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.
Works well, performed smoke testing 🚢 Thanks for taking this not critical but important tech debt issue 👍
…oks-from-constructors
…Automattic/woocommerce-payments into dev/7262-remove-hooks-from-constructors
Fixes #7262
Changes proposed in this Pull Request
Remove hook initialisation out of constructors for the
WCPay_Account
,*_Onboarding_Service
and*_Incentive_Service
.Testing instructions
WCPay_Account
class - I slightly altered the order of actions/filters to order them more logically, but we should double check to make sure nothing went wrong.npm run listen
, disconnect the currently connected account on the store, perform an onboarding, clear the cache. Ensure everything in the admin area looks good. Make a test purchase, and make sure it displays properly on thePayments > Transactions
page.npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge