-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Use translated model names in admin payment methods form #1975
Use translated model names in admin payment methods form #1975
Conversation
Need to rebase #1974 if we decide to make this change |
c3dc09d
to
1f45df4
Compare
Rebased, ready to review |
Looks even better with #2040 |
302f504
to
9842111
Compare
Currently the admin payment methods form uses a mix of payment_method and the payment methods class name params key. This is due to the STI nature of payment methods. By using the :as feature from Rails' form_for helper we remove code from the controller that merges these to kind of params hashes into one and reduce clutter in the form.
9842111
to
9b48a2c
Compare
Rebased again. Still ready for review |
- Use a checkbox in stead of two radio buttons to represent the active value. - Move autocapture select above check boxes - Use available space
9b48a2c
to
a81f974
Compare
We're going to backport and include this in 2.3.0. Since 2.3.0 includes the renames of the bogus payment method classes, it makes sense to include this and have them human readable (and also would avoid changing how they're displayed here in two separate consecutive releases). |
This PR is one of many that follow to remove the confusion around payment methods, payment providers and gateways we have for a long time in our code base.
There is lots of confusing parts in administrating payment methods:
Before
After