https://solidus.io logo
Join Slack
Powered by
Awesome - thanks, <@U0DRAKB26>! I'm trying to figu...
# support
t
Awesome - thanks, @elia! I'm trying to figure out what we would need here to migrate - it seems like with our integration, we have 
Spree::CreditCard
objects which I believe are created from the 
Spree::PaymentMethod::StripeCreditCard
class. Those objects do have a reference to the Stripe PaymentMethod in the 
gateway_payment_profile_id
field. (For us, those all happen to be 
card_XXX
because we are currently configured to pass 
v3_intents=false
in our payment method creation)
🧵 2
k
Moving to a thread: another option is to stick to v4 of SolidusStripe if that works for you and there’s no real need to use the new version. Do you envision any problem with this approach?
t
Nope, not necessarily - the only problem I could imagine here would be that being stuck on an older version of this gem could create dependency problems in the future. (For example, if something in this gem ends up being incompatible with a future Rails or Ruby update, say)
e
related: https://stackoverflow.com/a/57813102 looks like 
card_
tokens can be used instead of payment methods as-is
💯 1
t
Yup, that's my understanding as well!
I might take a stab at digging through this a bit and see what I can figure out. I think the hardest part here will just be figuring out how to update the Solidus PaymentMethod tables in the right way. I'll see what I can learn, and whether this is actually necessary or not. (I suspect this will end being a little tricky, but will likely help make our Stripe integration more robust at the end of the day!)
e
@Tom Wilson please keep us posted, feel free to ask for details of v5 internals, or send PRs to the repo 🙌
🙏 1
t
So - I seem to be sort of stuck here. I can't update to Solidus 4 while still using 
solidus_stripe v4
, because it requires 
solidus_core < 4
. And I can't update to 
solidus_stripe v5
without figuring out how to replace my Stripe integration. I had hoped to be able to update to Solidus 4 without taking the stripe update, but that seems impossible.
Am I missing something here? It seems like, in order to update our Solidus installation, we're going to first have to remove 
solidus_stripe
completely? Otherwise, this is going to be a pretty large update to take all at once...
I guess most accurately - I have to figure out how to update to 
solidus_stripe v5
first, and then can update to 
solidus_core v4
.
k
We can also update Solidus Stripe v4 to support Solidus v4
It’s just a dependency problem, or there’s anything more deep?
t
I'm not sure - I don't think there's anything deeper, but I've found three gems we use right now blocking us (
solidus_avatax_certified
, 
solidus_product_assembly
, and 
solidus_stripe
all require 
solidus_core < 4
today)
But at least from quick reads through the source in each case, there's nothing obvious jumping out at me as broken. 
solidus_stripe
was the scary one, given all the work in the new 
Solidus 4
gems. I wasn't sure how viable updating the dependency would be.
k
Got it, I think it’s just a matter of updating dependencies
I saw https://github.com/solidusio-contrib/solidus_product_assembly/pull/117, I think there’s a CI config misconfiguration. I’ll try to take a look as soon as possible.
e
solidus_stripe v4.4.1 is out with support for Solidus v4 https://github.com/solidusio/solidus_stripe/releases/tag/v4.4.1
t
Ooh, awesome - thanks @elia!
e
Please let me know if you bump into any issue with it! 🙌
Open in Slack
PreviousNext
Powered by