Change TopUpPaymentMethodsAdapter to use the same view holder as the PaymentMethodsAdapter to we can have the same UI and logic in both without major copy paste work.
What does this PR do?
A few sentences describing the overall goals of the pull request's commits.
Explain any technical decisions that were made and why (when it makes sense).
Where should the reviewer start?
[ ] TopUpFragment.kt
[ ] TopUpInteractor.kt
How should this be manually tested?
Flow on how to test this or QA Tickets related to this use-case: MOB-924
Change TopUpPaymentMethodsAdapter to use the same view holder as the PaymentMethodsAdapter to we can have the same UI and logic in both without major copy paste work.
What does this PR do?
A few sentences describing the overall goals of the pull request's commits.
Explain any technical decisions that were made and why (when it makes sense).
Where should the reviewer start?
How should this be manually tested?
Flow on how to test this or QA Tickets related to this use-case: MOB-924
What are the relevant tickets?
Tickets related to this pull-request: MOB-924
Questions:
Does this add new dependencies which need to be added? (Eg. new libs, new keys, etc.)
Code Review Checklist