Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Null Promotion Configuration in core #5744

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

mamhoff
Copy link
Contributor

@mamhoff mamhoff commented May 7, 2024

Summary

We want to use the legacy Spree::PromotionConfiguration in the solidus_legacy_promotions test suite.

Checklist

Check out our PR guidelines for more details.

The following are mandatory for all PRs:

The following are not always needed:

  • 📖 I have updated the README to account for my changes.
  • 📑 I have documented new code with YARD.
  • 🛣️ I have opened a PR to update the guides.
  • ✅ I have added automated tests to cover my changes.
  • 📸 I have attached screenshots to demo visual changes.

@github-actions github-actions bot added the changelog:solidus_core Changes to the solidus_core gem label May 7, 2024
@github-actions github-actions bot added the changelog:repository Changes to the repository not within any gem label May 16, 2024
mamhoff added 11 commits May 16, 2024 15:14
The existing promotion handlers are activated using either `#apply` or
`#activate`. The return value `#activate` is usually not read, and is
thus not really important, but that of `#apply` must be the handler
itself, so that e.g. the adjustments admin has access to any application
errors.
The one example here relies on the legacy promo system.
This is only here to facilitate moving from setting the calculatos on
the main Spree::Config object to a configuration. That's why it's
already deprecated.
We want to use the legacy `Spree::PromotionConfiguration` in the
solidus_legacy_promotions test suite.
This one spec should not live here.
@github-actions github-actions bot added the changelog:solidus_api Changes to the solidus_api gem label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:repository Changes to the repository not within any gem changelog:solidus_api Changes to the solidus_api gem changelog:solidus_core Changes to the solidus_core gem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant