You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
Solidus has a concept of Payment methods such as "CreditCard", "PayPal" and so on. This gem uses a single payment method for all of these, adding quite bit of complexity to e.g. the payment form when a store has more than just Braintree as a provider. Would you be open for a pull request that creates a Solidus payment method per payment method? So one could imagine instead of having just SolidusPaypalBraintree::Gateway the following three classes:
SolidusPaypalBraintree::CreditCard
SolidusPaypalBraintree::ApplePay
SolidusPaypalBraintree::Paypal
We have patched the gem in one of our projects to provide this. It makes analytics on an SQL level easier as well...
The text was updated successfully, but these errors were encountered:
I love this idea! Definitely would like to see this happen. I have never liked that this extension has an admin tab for overall setup, I could see that being unnecessary if we provided different payment classes.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Solidus has a concept of Payment methods such as "CreditCard", "PayPal" and so on. This gem uses a single payment method for all of these, adding quite bit of complexity to e.g. the payment form when a store has more than just Braintree as a provider. Would you be open for a pull request that creates a Solidus payment method per payment method? So one could imagine instead of having just
SolidusPaypalBraintree::Gateway
the following three classes:SolidusPaypalBraintree::CreditCard
SolidusPaypalBraintree::ApplePay
SolidusPaypalBraintree::Paypal
We have patched the gem in one of our projects to provide this. It makes analytics on an SQL level easier as well...
The text was updated successfully, but these errors were encountered: