-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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(payment): payment and session methods #6138
feat(payment): payment and session methods #6138
Conversation
…e-payment-collection-crud
…e-payment-collection-crud
# Conflicts: # packages/types/src/payment/mutations.ts
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
# Conflicts: # packages/payment/integration-tests/__tests__/services/payment-module/index.spec.ts # packages/payment/src/loaders/container.ts # packages/payment/src/services/payment-module.ts # packages/types/src/payment/mutations.ts
# Conflicts: # packages/payment/integration-tests/__tests__/services/payment-module/index.spec.ts
# Conflicts: # packages/payment/integration-tests/__tests__/services/payment-module/index.spec.ts
# Conflicts: # packages/payment/integration-tests/__tests__/services/payment-module/index.spec.ts # packages/payment/src/services/index.ts # packages/payment/src/services/payment-module.ts # packages/payment/src/types/repositories.ts
@carlos-r-l-rodrigues, can I get you to give this a review? Would like your eyes on the bulk methods for payment collections. Think some of them can get a bit nasty, especially when we introduce several calls to a third party provider. |
This is tricky, I told @fPolic that we could have bulk operations for that, but in a second thought I think that when we involve the providers the methods have to be single operations. |
I agree this is a tricky case. Right now, I am also leaning toward single operations. Let's discuss and address it in your follow up PR @fPolic that contains the provider implementation. |
What
Note