Documentation
Feedback
Guides

Release Notes
Release Notes
VTEX IO Release Notes- Week 38/2019
September, 27

{"base64":"  ","img":{"width":109,"height":20,"type":"svg","mime":"image/svg+xml","wUnits":"px","hUnits":"px","length":951,"url":"https://cdn.jsdelivr.net/gh/vtexdocs/dev-portal-content@main/images/vtex-io-release-notes-week-382019-0.png"}}

Did you ever imagine two VTEX IO Release Notes in one week? we. are. on. fire 🔥

Hope you will be able to set some time aside from your busy workweek to catch up with VTEX IO one more time.

Check out our key releases for week 38 of 2019 below:

New features 🚀

  • Fold block - Can you decide which store's block will be loaded and rendered after the user scroll down? Yes, you can: simply use the Fold block!
  • GraphQL types import - Save your precious time while developing! From now on, easily import GraphQL types from one app to another.
  • Product Customizer component - (finally) Display product attachments in your product page using the Product Customizer component.

Improvements ➕

  • Sandbox with OrderForm - The user's cart data can now be used in Sandbox components in a fast and simple way.
  • New Toast CSS handle - Customize the Toast component with a different style from the rest of the store thanks to the new CSS handle.
  • Toast component redirect - Greater control over user browsing is always magical. Use the BuyButton and ProductSummaryBuyButton new prop and redirect your user to any URL with a simple click on the Toast component.

Notable bug fixes 🐛

  • Free products on Google Shopping - Products are no longer being displayed as free on Google Shopping since the issue in our structured data that caused this bug was fixed.
  • i18n key props - When editing i18n fields, some users were facing an issue with their key props. There were a few scenarios in which the i18n key itself was being rendered raw instead of having its value displayed. This PR solves this issue.
  • __provideRuntime cache = The __provideRuntime function called the Messages service every time changes to a component were performed by the user, such as changing the Shelf title. To improve request responsiveness (previously at ~2s), this PR adds a local cache that returns the messages and avoids making the request whenever possible.
Was this helpful?
Yes
No
On this page