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

Rename PromotionConfiguration to LegacyPromotionConfiguration #5769

Merged

Conversation

mamhoff
Copy link
Contributor

@mamhoff mamhoff commented May 31, 2024

Summary

Earlier in the extraction process, I've defined a configuration object for the current promotion system and called it
Spree::Core::PromotionConfiguration. However, it is much more aptly named SolidusLegacyPromotions::Configuration, as it will be moved into that gem shortly. This way it's also clear when we move to the Spree::Core::NullPromotionConfiguration what we are changing.

@mamhoff mamhoff requested a review from a team as a code owner May 31, 2024 12:58
Copy link

codecov bot commented May 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.91%. Comparing base (9a42910) to head (029804b).
Report is 1 commits behind head on main.

Current head 029804b differs from pull request most recent head 7acf34b

Please upload reports for the commit 7acf34b to get more accurate results.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5769      +/-   ##
==========================================
- Coverage   88.91%   88.91%   -0.01%     
==========================================
  Files         711      711              
  Lines       16885    16884       -1     
==========================================
- Hits        15013    15012       -1     
  Misses       1872     1872              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mamhoff mamhoff force-pushed the rename-legacy-promotion-configuration branch 2 times, most recently from 1dfa0b8 to a905687 Compare June 3, 2024 12:02
@mamhoff mamhoff force-pushed the rename-legacy-promotion-configuration branch 2 times, most recently from 6ee92e1 to 029804b Compare June 3, 2024 14:52
Earlier in the extraction process, I've defined a configuration object
for the current promotion system and called it
`Spree::Core::PromotionConfiguration`. However, it is much more aptly
named `SolidusLegacyPromotions::Configuration`, as it will be moved into
that gem shortly. This way it's also clear when we move to the
`Spree::Core::NullPromotionConfiguration` what we are changing.
@mamhoff mamhoff force-pushed the rename-legacy-promotion-configuration branch from 029804b to 7acf34b Compare June 4, 2024 07:42
@github-actions github-actions bot added the changelog:solidus_core Changes to the solidus_core gem label Jun 4, 2024
Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense

@tvdeyen tvdeyen enabled auto-merge June 4, 2024 07:44
@tvdeyen tvdeyen merged commit d5ea410 into solidusio:main Jun 4, 2024
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:solidus_core Changes to the solidus_core gem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants