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

[CatalogPromotions] Add product to cart with discounted catalog price #13098

Conversation

Tomanhez
Copy link
Contributor

Q A
Branch? master
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
License MIT

@Tomanhez Tomanhez added the Feature New feature proposals. label Sep 14, 2021
@Tomanhez Tomanhez requested a review from a team as a code owner September 14, 2021 06:29
@Tomanhez Tomanhez force-pushed the customer-add-product-with-discounted-catalog-price branch 2 times, most recently from d66e101 to 0a12ba1 Compare September 14, 2021 07:09
When I view product "Wyborowa Vodka"
And I select "Wyborowa Apple" variant
Then the product variant price should be "$8,79"
And the product original price should be "$20.00"
Copy link
Member

Choose a reason for hiding this comment

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

I wonder, should we use price/original price words within the shop context. For a Customer/Visitor it's more like a discounted price/price, wdyt?

Copy link
Contributor

Choose a reason for hiding this comment

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

IMO the most important thing here is still Price, and this is something that really bothers Mr. Customer. The way how we say what was the price before is not so important - does the customer cares if it was called original? I don't think so. And in this case I would think about API first - where we are returning original price 🎉

Copy link
Member

Choose a reason for hiding this comment

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

Yes.... but! 😄 API-first is not an argument, as Behat scenarios are and should be always context-agnostic. What we should do in Behat scenarios is imitating the user behaviour. So, does the Customer sees the crossed-out price with a new one beside and thinks "the original price is X, but a price is now Y!"? Or it's more like "the price before was X, but a new, discounted price is Y!" 🚀 🐎

Of course, it's not a blocker for merge, but I believe we should really focus on Customer's behaviour and their vocabulary, to write perfect Behat scenarios :) 🖖

@Tomanhez Tomanhez force-pushed the customer-add-product-with-discounted-catalog-price branch 4 times, most recently from d2c416d to 43b8fa1 Compare September 14, 2021 10:58
@Tomanhez Tomanhez force-pushed the customer-add-product-with-discounted-catalog-price branch from 43b8fa1 to b77b125 Compare September 14, 2021 11:13
@arti0090 arti0090 force-pushed the customer-add-product-with-discounted-catalog-price branch 2 times, most recently from d22047b to 2335186 Compare September 14, 2021 11:31
@arti0090 arti0090 force-pushed the customer-add-product-with-discounted-catalog-price branch from 2335186 to 5c748dc Compare September 14, 2021 11:40
@Zales0123 Zales0123 merged commit 0c96399 into Sylius:master Sep 14, 2021
@Zales0123
Copy link
Member

Zales0123 commented Sep 14, 2021

Thank you, Tomasz and Artur! 🥇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature proposals.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants