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

Products are now requested with the exact price range from the filters #320

Conversation

fkloes
Copy link
Collaborator

@fkloes fkloes commented Oct 12, 2018

Description

This ticked fixes an issue where customers filtered products in category or search by price, but the request wasn't dispatched with the exact range that the user had picked. That caused that the filtered products lists didn't contain all available products within the price range which the user decided for.

Type of change

Please add an "x" into the option that is relevant:

  • [ x ] Bug Fix 🐛 (non-breaking change which fixes an issue)
  • [ ] New Feature 🚀 (non-breaking change which adds functionality)
  • [ ] Breaking Change 💥 (fix or feature that would cause existing functionality to not work as expected)
  • [ ] Polish 💅 (Just some cleanups)
  • [ ] Docs 📝 (Changes in the documentations)
  • [ ] Internal 🏠 Only relates to internal processes.

How to test it

  • open filters on a category or search page and change the price range slider
  • apply the filters and check, if the corresponding requests was dispatched with a range that is equal the the range you saw at the filter page.

- the getProducts pipeline is now called with the price range that is shown to the user
@fkloes fkloes added the bug Something isn't working label Oct 12, 2018
@fkloes fkloes self-assigned this Oct 12, 2018
return Object.keys(activeFilters).reduce((result, filterId) => {
const filter = activeFilters[filterId];

if (filterId === 'display_amount') {
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that here it would be better to check for a range filter type.

@coveralls
Copy link

coveralls commented Oct 12, 2018

Pull Request Test Coverage Report for Build 1170

  • 10 of 10 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.07%) to 47.285%

Totals Coverage Status
Change from base Build 1164: 0.07%
Covered Lines: 4127
Relevant Lines: 8316

💛 - Coveralls

@richardgorman richardgorman merged commit 08169b3 into PWA-327-Exchange-Router Oct 12, 2018
@richardgorman richardgorman deleted the PWA-1098-fix-get-products-requests-with-price-range branch October 12, 2018 09:38
SG-Noxoreos pushed a commit that referenced this pull request Oct 30, 2018
…gories

Pwa 475 error handling for categories
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants