-
Notifications
You must be signed in to change notification settings - Fork 122
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
COIOS-774: Pay by Bank - Confirmation Sheet #1876
COIOS-774: Pay by Bank - Confirmation Sheet #1876
Conversation
…by-bank-ui-update
AdyenComponents/PayByBank/US/PayByBankUSComponent+ConfirmationViewController.swift
Show resolved
Hide resolved
contentButtonStack.alignment = .fill | ||
|
||
view.addSubview(contentButtonStack) | ||
contentButtonStack.adyen.anchor(inside: view.layoutMarginsGuide, with: .init(top: 16, left: 0, bottom: 8, right: 0)) |
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.
Ideally this should go to some style constants in the future to avoid these magic numbers and make style changes easier.
model.continueHandler() | ||
} | ||
|
||
override public var preferredContentSize: CGSize { |
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.
What happens if we don't provide this manually?
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.
it will not get the height it needs
style: PayByBankUSComponent.Style, | ||
continueHandler: @escaping () -> Void | ||
) { | ||
let message: [String] = [ |
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.
Should this be localized?
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.
Good catch 😬
] | ||
|
||
self.headerImageUrl = headerImageUrl | ||
self.title = "Pay by Bank" |
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.
Same here and further down
@@ -419,7 +433,7 @@ extension ComponentManager: PaymentComponentBuilder { | |||
) | |||
} | |||
|
|||
private func createBoletoComponent(_ paymentMethod: BoletoPaymentMethod) -> BoletoComponent { | |||
func createBoletoComponent(_ paymentMethod: BoletoPaymentMethod) -> BoletoComponent { |
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.
We have a linter rule to prevent us from NOT having a scope defined, right?
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.
It does not catch here for some reason - it's in a private extension
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.
Maybe we can turn swiftlint warnings into errors so every time one doesn't need to even focus on this during code review.
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.
Easy to read and review, thanks 👍
/// Stored PayByBank payment. | ||
public struct StoredPayByBankPlaidPaymentMethod: StoredPaymentMethod { | ||
/// Stored PayByBank US payment. | ||
public struct StoredPayByBankUSPaymentMethod: StoredPaymentMethod { |
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.
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.
I found StoredPayByBankPlaidPaymentMethod
was added in the base branch. Let's rethink which branch to target when we run api diff? Options:
- develop (then we might have all long-living branch changes)
- latest release tag (then every time we have all development changes combined)
Or we can switch off api diff for all PRs not targeting develop and deal with all changes when we merge long-living branch into develop. The only concern I have is that usually it's a common sentiment to merge as fast as possible because "everything was reviewed", everyone has seen the code multiple times and naturally you just want to merge it asap.
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.
Yeah that's a tricky one - also thought about it.
I want to see the changes to the target branch but also agree that it would be nice to see the full change set to develop/release.
We could run it twice if the target branch is not develop and we're not in a release branch - so it creates 2 comments (one to the target branch and one to develop) - 🤔
Adyen/Core/Payment Methods/StoredPayByBankUSPaymentMethod.swift
Outdated
Show resolved
Hide resolved
👀 6 public changes detectedComparing
|
Quality Gate failedFailed conditions |
dc5436c
into
COIOS-774_pay-by-bank-improvements
Summary
Demo
Simulator.Screen.Recording.-.iPhone.16.Pro.-.2024-10-23.at.11.57.04.mp4
Ticket
COIOS-774