Upgrading acts_as_nested_set to awesome_nested_set #1927
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…. Upgrading to awesome_nested_set is backwards compatible and it allows refinery (which uses awesome_nested_set) to be mounted alongside spree
|
As far as I can tell, acts_as_nested_set hasn't been updated in quite a while. So I welcome this change :) |
radar
pushed a commit
that referenced
this pull request
Sep 7, 2012
…. Upgrading to awesome_nested_set is backwards compatible and it allows refinery (which uses awesome_nested_set) to be mounted alongside spree Fixes #1927
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am working on creating an application that uses both Spree and RefineryCMS. At the moment this requires a few small tweaks but otherwise works well. The only major conflict is that RefineryCMS uses awesome_nested_set whereas Spree uses acts_as_nested_set. They are namespaced and named the same so in some admin pages of refinery it causes it to use the wrong gem. Upgrading awesome_nested_set allows both apps to work nicely together and both test suites pass.