Closed nvandoorn closed 1 year ago
Cleaned up the commits, updated the changelog, this is ready to go!
@nvandoorn and I did a deep dive on the spec failures and it looks like something in Solidus 3.2 changed which results in our spec setup enqueueing a ReplaceTransactionJob
. It's possible that we just need to reset the job queue between specs so there is no leakage, but for now we've fixed the failures by just ensuring that calling the subject doesn't change the count.
What is the goal of this PR?
To gracefully handle updates to orders that were never reported at time of purchase.
How do you manually test these changes? (if applicable)
order_recalculated
)Merge Checklist