-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Update StripeConnect's FinancialConnections integration to work with public key override. #4379
Update StripeConnect's FinancialConnections integration to work with public key override. #4379
Conversation
🚨 New dead code detected in this PR: FinancialConnectionsPresenter.swift:21 warning: Parameter 'presentingViewController' is unused Please remove the dead code before merging. If this is intentional, you can bypass this check by adding the label ℹ️ If this comment appears to be left in error, double check that the flagged code is actually used and/or make sure your branch is up-to-date with |
StripeConnect/StripeConnect/Source/Internal/FinancialConnectionsPresenter.swift
Outdated
Show resolved
Hide resolved
StripeConnect/StripeConnect/Source/Internal/FinancialConnectionsPresenter.swift
Outdated
Show resolved
Hide resolved
3e17301
to
a3e8b57
Compare
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.
lgtm -- not sure if you wanted to add an xctassertequal on the client secret. If so, lmk and I'll reshipit
Looks like |
a3e8b57
to
2cf8a48
Compare
2cf8a48
to
b514231
Compare
XCTAssert(compManager.apiClient == componentManager.apiClient) | ||
XCTAssert(compManager.publicKeyOverride == componentManager.publicKeyOverride) |
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.
Doublechecking – STPAPIClient subclasses NSObject and doesn't override isEqual
, so I think this should just do pointer-comparison, right? Just want to make sure the equality comparison does what we think it should.
Non-blocking: Also, if we're using ==
anyway, this could be XCTAssertEqual
which would provide a better failure message if the test fails.
XCTAssert(compManager.apiClient == componentManager.apiClient) | |
XCTAssert(compManager.publicKeyOverride == componentManager.publicKeyOverride) | |
XCTAssertEqual(compManager.apiClient, componentManager.apiClient) | |
XCTAssertEqual(compManager.publicKeyOverride, componentManager.publicKeyOverride) |
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 this should be doing pointer comparison.
📸 Snapshot TestNo snapshots generated
🛸 Powered by Emerge Tools |
Summary