-
-
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
Confused about Gateway / Provider deprecations #2476
Comments
This was changed in Solidus 2.3 for more clear naming (See #2000). There should be no difference other than naming |
Thanks @jhawthorn - to use Stripe would I do:
ie - How do I refer to a specific gateway in the new format? Also - as i understand it - that will only fix one of the deprecations. How would I fix the others? |
@hhff The deprecations probably do not come out of code you wrote yourself, but out of the |
I still don't understand I'm sorry. I'm using How do I create a Stripe Gateway in the new naming convention? |
@hhff |
Hi All, Noticed 1.3 is up on ruby gems, so I thought I'd take another stab at getting these deprecation warnings out of my Tests! After updating, I'm having this same problem. This is the code change I'm making:
The Thank you! Solidus Rules! |
Closing this one, there is https://github.com/solidusio-contrib/solidus_stripe that is compatible with the new naming and could be taken as a reference, just in case someone else is still looking for an answer. |
Steps to reproduce
I'm making the switch from Spree to Solidus, and as part of the codebase (seeds, etc) we create orders programatically.
In Spree, I would do:
System configuration
Solidus Version: 2.4.2
Deprecations produced:
I had a look around and couldn't find much documentation on the change. How should I re-write the above in the new Solidus way so that it wont output deprecations?
Thanks for the hard work!
The text was updated successfully, but these errors were encountered: