| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Sid is more familiar with Facilitated Payments code than I am, so I'm going to defer this review to him and move myself to CC. Thank you!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I don't think these belong to a FopSelectorViewBinder. The header/continue button/additional info are common properties of the PaymentMethodsView and thus should be usable for multiple screens instead of just the FopSelector.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I don't think these belong to a FopSelectorViewBinder. The header/continue button/additional info are common properties of the PaymentMethodsView and thus should be usable for multiple screens instead of just the FopSelector.
Thanks for the feedback! You're right — header, continue button, and additional info shouldn't be tied to FopSelector since they're reusable across screens.
Extracted them into per-item-type ViewBinder classes following the existing pattern (like BankAccountViewBinder).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Move FOP selector list item binding out of
FacilitatedPaymentsPaymentMethodsViewBinder into a dedicated
FacilitatedPaymentsFopSelectorViewBinder.
This keeps the payment methods view binder focused on screen-level
sequence view setup while the FOP selector screen owns binding for
its header, additional info, continue button, and footer items.Please update the commit message now that the implementation has changed.
jingjing guI don't think these belong to a FopSelectorViewBinder. The header/continue button/additional info are common properties of the PaymentMethodsView and thus should be usable for multiple screens instead of just the FopSelector.
Thanks for the feedback! You're right — header, continue button, and additional info shouldn't be tied to FopSelector since they're reusable across screens.
Extracted them into per-item-type ViewBinder classes following the existing pattern (like BankAccountViewBinder).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
jingjing guI don't think these belong to a FopSelectorViewBinder. The header/continue button/additional info are common properties of the PaymentMethodsView and thus should be usable for multiple screens instead of just the FopSelector.
Siddharth ShahThanks for the feedback! You're right — header, continue button, and additional info shouldn't be tied to FopSelector since they're reusable across screens.
Extracted them into per-item-type ViewBinder classes following the existing pattern (like BankAccountViewBinder).
jingjing guThanks for doing this!
Thanks for the reminder! Updated.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Is there anything in particular you need my review for? Sid (already LGTM'd) is a code owner for all of these files, as far as I can tell.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I don't think you actually need chrome/OWNERS. So replacing myself with someone from chrome/android/OWNERS.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Is there anything in particular you need my review for? Sid (already LGTM'd) is a code owner for all of these files, as far as I can tell.
| Code-Review | +1 |
Lei ZhangIs there anything in particular you need my review for? Sid (already LGTM'd) is a code owner for all of these files, as far as I can tell.
I think the CL just needs a second CR+1.
Ah, I missed that; thanks!
I would rather Sky be the second CR+1, but in case you're blocked and this is urgent, I'll CR+1 because I trust Sid's judgement and nothing jumps out at me in the CL itself.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Move FOP selector list item binding out of
FacilitatedPaymentsPaymentMethodsViewBinder into a dedicated
FacilitatedPaymentsFopSelectorViewBinder.
This keeps the payment methods view binder focused on screen-level
sequence view setup while the FOP selector screen owns binding for
its header, additional info, continue button, and footer items.Please update the commit message now that the implementation has changed.
Thanks for the reminder! Updated.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[browser] Split facilitated payments FOP selector binder
Extract per-item-type ViewBinder classes from
FacilitatedPaymentsPaymentMethodsViewBinder, following the existing
pattern used by BankAccountViewBinder and similar classes:
- HeaderViewBinder: binds header items
- ContinueButtonViewBinder: binds the continue button
- AdditionalInfoViewBinder: binds additional info items
- FooterViewBinder: binds footer items
This keeps FacilitatedPaymentsPaymentMethodsViewBinder focused on
screen-level setup and makes the individual binders reusable across
different screens.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |