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

CATALOG-1447 - Update product cards to use price ranges #1143

Merged
merged 1 commit into from
Jan 11, 2018
Merged

CATALOG-1447 - Update product cards to use price ranges #1143

merged 1 commit into from
Jan 11, 2018

Conversation

bookernath
Copy link
Contributor

@bookernath bookernath commented Jan 3, 2018

What?

-Remove "as low as" feature (no longer needed with price ranges)
-Add new "price range" boolean theme editor setting, defaulting to true, to display ranges
-Augment price component to support ranges if available and enabled (graceful fallback for stores not enabled)
-Update schema.org to use PriceSpecification so that we can correctly support ranges and also inc tax/exc tax

Tickets / Documentation

Add links to any relevant tickets and documentation.

Screenshots (if appropriate)

image

Other important notes

  • This effectively removes support for display of Retail Price when there's a price range. This is intentional, because it might not make too much sense to display a singular Retail Price in conjunction with a price range. As retail prices get range support, we can add it back in.
  • Similarly, I haven't yet done anything for the behavior of Sale Price

@@ -1,3 +1,35 @@
{{#with price_range}}
{{min.formatted}} - {{max.formatted}}
{{/with}}
{{#and price_range.min.with_tax price_range.max.with_tax}}
Copy link
Contributor

Choose a reason for hiding this comment

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

since we're using a {{#with price_range}} above we can do {{#and min.with_tax max.with_tax}} instead and {{#and}} seems fine to me

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, will update

@bigbot
Copy link

bigbot commented Jan 4, 2018

Autotagging @bigcommerce/storefront-team @davidchin

@bookernath
Copy link
Contributor Author

Screenshot from integration:

image

@bookernath bookernath changed the title (WIP) CATALOG-1447 - Update product cards to use price ranges CATALOG-1447 - Update product cards to use price ranges Jan 5, 2018
Copy link
Contributor

@mjschock mjschock left a comment

Choose a reason for hiding this comment

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

LGTM

@bookernath bookernath changed the title CATALOG-1447 - Update product cards to use price ranges (WIP) CATALOG-1447 - Update product cards to use price ranges Jan 8, 2018
@bookernath bookernath changed the title (WIP) CATALOG-1447 - Update product cards to use price ranges CATALOG-1447 - Update product cards to use price ranges Jan 8, 2018
{{#and price_range.min.without_tax price_range.max.without_tax}}
<abbr title="{{lang 'products.excluding_tax'}}">{{lang 'products.price_with_tax' tax_label=price_range.min.tax_label}}</abbr>
{{else if schema_org}}
<meta itemprop="availability" content="{{product.availability}}">
Copy link
Contributor

@junedkazi junedkazi Jan 9, 2018

Choose a reason for hiding this comment

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

I am wondering if it makes sense to move the meta into a price schema component.

Copy link
Contributor

@junedkazi junedkazi left a comment

Choose a reason for hiding this comment

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

Overall this looks good to me.

-Remove "as low as" feature
-Add new "price range" boolean theme editor setting, defaulting to true, to display ranges
-Augment price component to support ranges if available and enabled
-Update schema.org to use PriceSpecification so that we can correctly support ranges and also inc tax/exc tax
@zackangelo zackangelo merged commit 3350ea5 into bigcommerce:master Jan 11, 2018
@bookernath bookernath deleted the price-ranges-cornerstone branch January 11, 2018 05:00
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