Let promotion handler decide whether it can add a coupon to an order #5684
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.
Summary
We have the method
Spree::Order#can_add_coupon?
that tells us whether an order can even accept a promotion code. Unfortunately, it directly references theSpree::Promotion
class that is slated to be moved tosolidus_legacy_promotions
. Rather than adding a new class, I add another method to the coupon promotion handler class that does this.I'm also adding the same method to the
NullPromotionHandler
for API parity.Lastly, I realized that not all promotion handlers in core share the same API, so I alias
activate
toapply
so that theNullPromotionHandler
can be a stand-in for all promotion handlers.Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: