Skip to content

Solidus 2.2 support#1

Open
fastjames wants to merge 22 commits intonebulab:v1.1from
geminimvp:solidus_22
Open

Solidus 2.2 support#1
fastjames wants to merge 22 commits intonebulab:v1.1from
geminimvp:solidus_22

Conversation

@fastjames
Copy link

I don't know how active this repo is, but I wanted to offer my cleanup work to get this working with Solidus 2.2. I based my work off of https://github.com/Follain/solidus_cangaroo/tree/v2.2.1 which seemed like the most recent branch in this direction. All specs are green, and I get one remaining deprecation notice from somewhere within activesupport.

I did make a few changes that might not be the right thing to do:

  1. As I mentioned, I started my work from a branch on a fork, which itself sprang from the v1.1 branch here. I considered going back to master but it felt like I was redoing a lot of the things in the branch.
  2. I couldn't find any other references to the skip_single_cart_validiation method (called from AddOrderHandler) so I removed it.
  3. I modified the OrderSerializer spec slightly, leaving out the shipment adustment that was previously instantiated.
  4. I tried to make minor style adjustments such as line lengths where I touched the code and only in those places.
  5. I added a dependency on Rails 5.0 in the gemspec. This is probably wrong.

If this work can be used by others, I'm happy to make changes to the PR. I'd hate for someone else to have to do the same stuff over again.

Jeff Dutil and others added 22 commits February 13, 2015 11:08
Adjusts the gem's dependency manifest, and makes adjustments to get the
test suite to pass.

Fixes #74
In 2-4-stable a code field was used for shipping methods. Here is the intention:

> The expectation, like a sku, is that a shipping_method.code could represent an immutable value that is safe to bind against when figuring
> out what shipping method to use.

Fixes #78
Continuing the work from Follain, we update specs and tweak code where
required to achieve 100% specs passing.
When importing images, I seem to get one of two different exceptions
depending on... I'm not sure what. How the test is run? Anyway, it's
better to be consistent so we re-raise one of the exceptions as the
other at that point.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants