-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat(router): [V2] Introduce V2Auth and use it for payment_methods_list_enabled #7038
base: main
Are you sure you want to change the base?
Conversation
Changed Files
|
@@ -1,5 +1,7 @@ | |||
#[cfg(feature = "v1")] | |||
pub use api_models::payments::PaymentsRequest; | |||
#[cfg(feature = "v1")] | |||
pub use api_models::payments::{PaymentListResponse, PaymentListResponseV2, PaymentsResponse}; |
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.
why do we need to re export this, ideally we should not have any re exports
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.
Needed to move these out of the existing re-exports to add the v1
feature gate. Removing re-exports can be taken up as a separate task
Type of Change
Description
Added an enum
V2Auth
(name subject to change) to encapsulate different authentication scenarios. Currently only works for Client Authentication usingpublishable_key
andephemeral_key
inAuthorization
headerAdditional Changes
Motivation and Context
Closes #7037
How did you test it?
1a. Payment method intent create request:
1b. Payment method intent create response:
2a. List payment methods enabled request:
2b. List payment methods enabled response:
Checklist
cargo +nightly fmt --all
cargo clippy