Specify inheritance for Spree::Promotion #2572
Merged
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.
it makes clear that Spree::Promotion inherit from Spree::Base and then
ActiveRecord.
With a promotion decorator present in the app, there are cases where calling a class method from an another gem on
Spree::Promotion
result in aNoMethodError
. This is because the receiver has no superclass(just Object) and not Spree::Base as expected. It probably depend on which definition is loaded first.The app has the following definitions:
and a custom action defined like the default on solidus_core
In some cases this results in a
NoMethodError
whenPromotion
receivesfoo
and the same when it receivescount
or any other active record methods.Adding
< Spree::Base
in the custom actions and rules in the app was enough to solve the issue, but I think that Spree::Promotion should inherit from Spree::Base in solidus_core as well.