-
Notifications
You must be signed in to change notification settings - Fork 219
Payment method content could potentially become a bottlen... #4359
Comments
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
This issue has been marked as Internal: After 10 days with no activity this issue will be automatically be closed. |
Find a way to Memoize Express Payment Method Content
Payment method content could potentially become a bottleneck if lots of logic is ran in the content component. ItCurrently re-renders excessively but is not easy to useMemo because paymentMethodInterface could become stale.paymentMethodInterface itself also updates on most renders.
https://github.com/woocommerce/woocommerce-gutenberg-products-block/blob/a8c49055cddf06bf183df1c67ba7bcd7cdb757e1/assets/js/blocks/cart-checkout/payment-methods/express-payment-methods.js#L114-L129
🚀 This issue was generated by the automations bot based on a
todo
comment in a8c4905 when #4228 was merged. cc @mikejolleyThe text was updated successfully, but these errors were encountered: