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

feature(bctheme): BCTHEME-45 Update CornerStone to Utilize Existence of sale_price property for Determining Product/Variant Sale Status #1719

Merged
merged 3 commits into from
Jul 13, 2020

Conversation

yurytut1993
Copy link
Contributor

@yurytut1993 yurytut1993 commented Jul 10, 2020

What?

@BC-tymurbiedukhin @golcinho @bc-alexsaiannyi @junedkazi

Update CornerStone to Utilize Existence of sale_price property for Determining Product/Variant Sale Status.
I have changed the way how we check product status - on sale or not. And when sale properties (sale_price_with_tax & sale_price_without_tax) are not exist or their value equal to 0 - product status is NOT on sale. In other case we should add a sale badge

Tickets / Documentation

Ticket

@bigbot
Copy link

bigbot commented Jul 10, 2020

Autotagging @bigcommerce/storefront-team @davidchin

golcinho
golcinho previously approved these changes Jul 10, 2020
…ce property for Determining Product/Variant Sale Status (indents update)
@yurytut1993
Copy link
Contributor Author

@golcinho can you please approve current pr one more time - I just added new commit with new indents to make code more readable

@yurytut1993 yurytut1993 changed the title feature(bctheme): Update CornerStone to Utilize Existence of sale_price property for Determining Product/Variant Sale Status feature(bctheme): BCTHEME-45 Update CornerStone to Utilize Existence of sale_price property for Determining Product/Variant Sale Status Jul 10, 2020
@junedkazi junedkazi merged commit cf949a5 into bigcommerce:master Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants