id
stringlengths 12
53
| messages
listlengths 3
3
|
|---|---|
code_doc-prop-component_c6e4475c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/node/typings/global.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ninterface GithubAuthHeader {\n Authorization: string,\n 'X-Vtex-Use-Https': string\n}\n\ninterface DocsBotConfigs {\n pem: string,\n reposWithoutReadMe: string[]\n}\n\n```"
}
] |
code_doc-prop-component_4d86950a
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/node/utils/utils.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport const getAppConfigs = async (ctx: Context): Promise <DocsBotConfigs> => {\n return ctx.clients.vbase.getJSON(\n 'countdown', 'configs'\n )\n}\n\nexport const updateConfigs = async (ctx: Context, data: any): Promise <any> => {\n const configs = await getAppConfigs(ctx)\n return ctx.clients.vbase.saveJSON(\n 'countdown',\n 'configs',\n {\n ...configs,\n ...data,\n }\n )\n}\n\n```"
}
] |
code_doc-prop-component_3ea1f3d8
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/node/resolvers/gif.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport const gif = async (\n _: any,\n { query }: { query: string},\n { clients: { giphy }}: Context\n) => giphy.translateGif(query)\n```"
}
] |
code_doc-prop-component_3036d10e
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/node/handlers/gif.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nimport {\n json\n} from 'co-body'\n\nexport async function handleGif(ctx: Context, next: () => Promise < any > ) {\n const body = await json(ctx.req)\n\n const {\n query,\n } = body\n\n ctx.set('cache-control', 'no-cache,no-store')\n const url = await ctx.clients.giphy.translateGif(query)\n\n ctx.status = 200\n ctx.body = {\n url,\n }\n\n await next()\n}\n```"
}
] |
code_doc-prop-component_c557dce7
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/typings/storefront.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nimport { FunctionComponent } from 'react'\n\ndeclare global {\n interface StorefrontFunctionComponent<P = {}> extends FunctionComponent<P> {\n getSchema?(props: P): object\n schema?: object\n }\n\n interface StorefrontComponent<P = {}, S = {}> extends Component<P, S> {\n getSchema?(props: P): object\n schema: object\n }\n}\n\n```"
}
] |
code_doc-prop-component_483e2032
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/typings/vtex.render-runtime.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\n/* Typings for `render-runtime` */\ndeclare module 'vtex.render-runtime' {\n import { Component, ComponentType, ReactElement, ReactType } from 'react'\n\n export interface NavigationOptions {\n page: string\n params?: any\n }\n\n export interface RenderContextProps {\n runtime: {\n navigate: (options: NavigationOptions) => void\n }\n }\n\n interface ExtensionPointProps {\n id: string\n [key: string]: any\n }\n\n export const ExtensionPoint: ComponentType<ExtensionPointProps>\n\n interface ChildBlockProps {\n id: string\n }\n\n export const ChildBlock: ComponentType<ChildBlockProps>\n export const useChildBlock = function({ id: string }): object {}\n\n export const Helmet: ReactElement\n export const Link: ReactType\n export const NoSSR: ReactElement\n export const RenderContextConsumer: ReactElement\n export const canUseDOM: boolean\n export const withRuntimeContext: <TOriginalProps extends {}>(\n Component: ComponentType<TOriginalProps & RenderContextProps>\n ) => ComponentType<TOriginalProps>\n}\n\n```"
}
] |
code_doc-prop-component_bf276880
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/typings/global.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport interface TimeSplit {\n hours: string,\n minutes: string,\n seconds: string \n}\n```"
}
] |
code_doc-prop-component_ebbb2632
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/typings/css.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ndeclare module '*.css' {\n const css: any\n export default css\n}\n\n```"
}
] |
code_doc-prop-component_9c2b1171
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/typings/graphql.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ndeclare module '*.graphql' {\n import { DocumentNode } from 'graphql'\n\n const value: DocumentNode\n export default value\n}\n\n```"
}
] |
code_doc-prop-component_de4ec235
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/typings/vtex.styleguide.d.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ndeclare module 'vtex.styleguide' {\n import { ComponentType } from 'react'\n\n export const Input: ComponentType<InputProps>\n\n interface InputProps {\n [key: string]: any\n }\n}\n\n```"
}
] |
code_doc-prop-component_60421b04
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/queries/gifs.gql from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```graphql\nquery getGifTranslation($query:String) {\n gif (query: $query) {\n url\n }\n}\n```"
}
] |
code_doc-prop-component_a3442260
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of doc-prop-component/react/utils/time.ts from the doc-prop-component VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nimport { TimeSplit } from \"../typings/global\"\n\nconst SECONDS_IN_MINUTE = 60\nconst SECONDS_IN_HOUR = 60 * SECONDS_IN_MINUTE\n\nexport const parseTimeRemaining = (totalSeconds: number) : TimeSplit => {\n const hours = Math.floor(totalSeconds / SECONDS_IN_HOUR)\n const minutes = Math.floor(((totalSeconds % SECONDS_IN_HOUR) / SECONDS_IN_MINUTE))\n const seconds = Math.floor(((totalSeconds % SECONDS_IN_HOUR) % SECONDS_IN_MINUTE))\n return {\n hours: fillWithZero(2, hours),\n minutes: fillWithZero(2, minutes),\n seconds: fillWithZero(2, seconds)\n } \n}\n\nconst fillWithZero = (digits: number, number: number) : string => { \n const filled = '0' + number \n return filled.slice(filled.length - digits)\n}\n```"
}
] |
code_shipping-calculator_42b9ed8a
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/hu.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Kézbesítés\",\n \"store/shipping-calculator.deliveryFor\": \"Lehetőségek a következőhöz:\",\n \"store/shipping-calculator.edit\": \"szerkesztés\",\n \"store/shipping-calculator.estimate\": \"becslés\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"Kézbesítési lehetőségek megtekintése\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {A termék nem} other {Egy termék sem}} kézbesíthető erre a címre.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {Egy termék, amelyet nem lehetett kézbesíteni erre a címre, kiemelésre került} other {# termék, amelyet nem lehetett kézbesíteni erre a címre, kiemelésre került}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {lehetőség} other {lehetőség}} a hátralevő {numberOfItems, plural, one {termékhez} other {termékhez}}\",\n \"admin/editor.shipping-calculator.label\": \"Kézbesítés\",\n \"admin/editor.shipping-calculator.title\": \"Cím\"\n}\n\n```"
}
] |
code_shipping-calculator_5dee3678
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/ja.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"配送\",\n \"store/shipping-calculator.deliveryFor\": \"オプション\",\n \"store/shipping-calculator.edit\": \"編集する\",\n \"store/shipping-calculator.estimate\": \"推定\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"配送オプションを閲覧\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {この製品} other {すべての製品}} をこちらの住所に配送できません。\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {この住所に配送できない製品がハイライトされています} other {この住所に配送できない # 個の製品がハイライトされています}}。\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"残りの {numberOfItems, plural, one {製品} other {製品}} のための {numberOfOptions, plural, one {オプション} other {オプション}}\",\n \"admin/editor.shipping-calculator.label\": \"配送\",\n \"admin/editor.shipping-calculator.title\": \"タイトル\"\n}\n\n```"
}
] |
code_shipping-calculator_7256f2c6
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/fi.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Toimitus\",\n \"store/shipping-calculator.deliveryFor\": \"Asetukset kohteelle\",\n \"store/shipping-calculator.edit\": \"muokkaa\",\n \"store/shipping-calculator.estimate\": \"arvio\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"Näytä toimitusvaihtoehdot\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {Tuotetta} other {Tuotteita}} ei voida toimittaa tähän osoitteeseen.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {Tuote, jota ei voida toimittaa tähän osoitteeseen, näkyy korostettuna} other {# tuotetta, joita ei voida toimittaa tähän osoitteeseen, näkyy korostettuna}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {Vaihtoehto} other {Vaihtoehdot}} jäljellä olevalle / oleville {numberOfItems, plural, one {tuotteelle} other {tuotteille}}\",\n \"admin/editor.shipping-calculator.label\": \"Toimitus\",\n \"admin/editor.shipping-calculator.title\": \"Nimi\"\n}\n\n```"
}
] |
code_shipping-calculator_d926f13f
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/pt.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Entrega\",\n \"store/shipping-calculator.deliveryFor\": \"Opções para\",\n \"store/shipping-calculator.edit\": \"alterar\",\n \"store/shipping-calculator.estimate\": \"calcular\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"Ver opções de entrega\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {O produto não pode ser entregue} other {Nenhum dos produtos podem ser entregues}} nesse endereço.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {Um produto que não pode ser entregue nesse endereço foi destacado} other {# produtos que não podem ser entregues nesse endereço foram destacados}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {Opção} other {Opções}} para {numberOfItems, plural, one {o produto restante} other {os produtos restantes}}\",\n \"admin/editor.shipping-calculator.label\": \"Entrega\",\n \"admin/editor.shipping-calculator.title\": \"Título\"\n}\n\n```"
}
] |
code_shipping-calculator_1180e4dd
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/en.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Delivery\",\n \"store/shipping-calculator.deliveryFor\": \"Options for\",\n \"store/shipping-calculator.edit\": \"edit\",\n \"store/shipping-calculator.estimate\": \"estimate\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"View delivery options\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {The product} other {All the products}} can't be delivered to this address.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {A product that can't be delivered to this address was highlighted} other {# products that can't be delivered to this address were highlighted}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {Option} other {Options}} for remaining {numberOfItems, plural, one {product} other {products}}\",\n \"admin/editor.shipping-calculator.label\": \"Delivery\",\n \"admin/editor.shipping-calculator.title\": \"Title\"\n}\n\n```"
}
] |
code_shipping-calculator_93a2f6fe
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/ro.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Livrare\",\n \"store/shipping-calculator.deliveryFor\": \"Opțiuni pentru\",\n \"store/shipping-calculator.edit\": \"editează\",\n \"store/shipping-calculator.estimate\": \"estimat\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"Vezi opțiunile de livrare\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {Produs} other {Niciun produs}} nu pot fi livrat la această adresă.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {Un produs care nu poate fi livrat la această adresă va fi evidențiat} other {# produse care nu poate fi livrate la această adresă vor fi evidențiate}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {Opțiune} other {Opțiuni}} pentru {numberOfItems, plural, one {produsul} other {produsele}} rămase\",\n \"admin/editor.shipping-calculator.label\": \"Livrare\",\n \"admin/editor.shipping-calculator.title\": \"Titlu\"\n}\n\n```"
}
] |
code_shipping-calculator_f8b81188
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/ko.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"배달\",\n \"store/shipping-calculator.deliveryFor\": \"옵션\",\n \"store/shipping-calculator.edit\": \"편집\",\n \"store/shipping-calculator.estimate\": \"견적\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"배송 옵션 보기\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {제품이} other {모든 제품이}} 이 주소로 배송될 수 없습니다.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {개의 이 주소로 배송할 수 없는 제품이 강조 표시되었습니다} other {#개의 이 주소로 배송할 수 없는 제품이 강조 표시되었습니다}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"남은 {numberOfItems, plural, one {제품} other {제품}} {numberOfOptions, plural, one {옵션} other {옵션}}\",\n \"admin/editor.shipping-calculator.label\": \"배달\",\n \"admin/editor.shipping-calculator.title\": \"제목\"\n}\n\n```"
}
] |
code_shipping-calculator_c899cb64
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/da.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Levering\",\n \"store/shipping-calculator.deliveryFor\": \"Indstillinger for\",\n \"store/shipping-calculator.edit\": \"rediger\",\n \"store/shipping-calculator.estimate\": \"estimeret\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"Vælg leveringsmuligheder\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {Produktet} other {Alle produkterne}} kan ikke blive leveret til denne adresse.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {Et produkt, der ikke kan leveres til denne adresse, blev fremhævet} other {# produkter, der ikke kan leveres til denne adresse, blev fremhævet}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {Indstilling} other {Indstillinger}} for resterende {numberOfItems, plural, one {produkt} other {produkter}}\",\n \"admin/editor.shipping-calculator.label\": \"Levering\",\n \"admin/editor.shipping-calculator.title\": \"Titel\"\n}\n\n```"
}
] |
code_shipping-calculator_a6be1423
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/es.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"Entrega\",\n \"store/shipping-calculator.deliveryFor\": \"Opciones para\",\n \"store/shipping-calculator.edit\": \"cambiar\",\n \"store/shipping-calculator.estimate\": \"calcular\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"Ver opciones de entrega\",\n \"store/shipping-calculator.allItemsUnavailable\": \"{numberOfUnavailableItems, plural, one {El producto no} other {Ningún de los productos}} se puede entregar en esta dirección.\",\n \"store/shipping-calculator.unavailableItems\": \"Se {numberOfUnavailableItems, plural, one {encuentra resaltado un producto que no se puede} other {encuentran marcados # productos que no se pueden}} entregar en esta dirección.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {Opción} other {Opciones}} para {numberOfItems, plural, one {el producto restante} other {productos restantes}}\",\n \"admin/editor.shipping-calculator.label\": \"Entrega\",\n \"admin/editor.shipping-calculator.title\": \"Título\"\n}\n\n```"
}
] |
code_shipping-calculator_20196a3b
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/messages/ar.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store/shipping-calculator.delivery\": \"التسليم\",\n \"store/shipping-calculator.deliveryFor\": \"خيار لـ\",\n \"store/shipping-calculator.edit\": \"تعديل\",\n \"store/shipping-calculator.estimate\": \"تقدير\",\n \"store/shipping-calculator.viewDeliveryOptions\": \"عرض خيارات التسليم\",\n \"store/shipping-calculator.allItemsUnavailable\": \"لا يمكن تسليم {numberOfUnavailableItems, plural, one {المنتج} other {المنتجات}} لهذا العنوان.\",\n \"store/shipping-calculator.unavailableItems\": \"{numberOfUnavailableItems, plural, one {تم تمييز المنتج الذي لا يمكن تسليمه إلى هذا العنوان} other {# تم تمييز المنتجات الأخرى التي لا يمكن تسليمها إلى هذا العنوان}}.\",\n \"store/shipping-calculator.optionsForRemainingProducts\": \"{numberOfOptions, plural, one {خيار} other {خيارات}} لـ {numberOfItems, plural, one {للمنتج} other {المنتجات}} المتبقي(ة)\",\n \"admin/editor.shipping-calculator.label\": \"التسليم\",\n \"admin/editor.shipping-calculator.title\": \"العنوان\"\n}\n\n```"
}
] |
code_shipping-calculator_7d88ad8c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/docs/README.md from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n# VTEX IO Base Component\n<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->\n[](#contributors-)\n<!-- ALL-CONTRIBUTORS-BADGE:END -->\n\nThis demo component shows you how to make a simple yet complete VTEX IO component.\n\nIt shows a simple demonstration of the following features:\n\n- Declaring a component interface in `store/interfaces.json`.\n- Declaring a schema to receive props via Storefront.\n- Using the `messages` feature to have localized strings.\n- Using an NPM package like `react-intl`\n- Using another VTEX IO App like `vtex.styleguide`.\n- Using CSS Modules to make your component customizable via CSS on a store theme.\n- Using tachyons tokens to quickly style your components.\n## Contributors ✨\n\nThanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):\n\n<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->\n<!-- prettier-ignore-start -->\n<!-- markdownlint-disable -->\n<!-- markdownlint-enable -->\n<!-- prettier-ignore-end -->\n<!-- ALL-CONTRIBUTORS-LIST:END -->\n\nThis project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind are welcome!\n\n```"
}
] |
code_shipping-calculator_5e1f7834
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/Shipping.tsx from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React, { ReactNode } from 'react'\nimport { FormattedMessage, defineMessages } from 'react-intl'\nimport { OrderShipping } from 'vtex.order-shipping'\nimport { useAddressRules } from 'vtex.checkout-shipping'\nimport { AddressContext } from 'vtex.address-context'\nimport { Loading } from 'vtex.render-runtime'\nimport { OrderForm } from 'vtex.order-manager'\n\nconst { useOrderForm } = OrderForm\nconst { useOrderShipping } = OrderShipping\n\nconst messages = defineMessages({\n delivery: {\n defaultMessage: 'Delivery',\n id: 'store/shipping-calculator.delivery',\n },\n label: {\n defaultMessage: '',\n id: 'admin/editor.shipping-calculator.label',\n },\n title: {\n defaultMessage: '',\n id: 'admin/editor.shipping-calculator.title',\n },\n})\n\ninterface ShippingProps {\n children: ReactNode\n title: string\n}\n\nconst Shipping: React.VFC<ShippingProps> = ({\n children,\n title = messages.delivery.id,\n}) => {\n const { selectedAddress, countries } = useOrderShipping()\n const addressRules = useAddressRules()\n\n if (addressRules == null) {\n return <Loading />\n }\n\n return (\n <AddressContext.AddressContextProvider\n address={selectedAddress}\n countries={countries}\n rules={addressRules}\n >\n <div className=\"flex flex-column c-on-base\">\n <h5 className=\"t-heading-5 mt0 mb6\">\n <FormattedMessage id={title} />\n </h5>\n {children}\n </div>\n </AddressContext.AddressContextProvider>\n )\n}\n;(Shipping as any).schema = {\n title: messages.label.id,\n}\n\nconst ShippingWithLoading: typeof Shipping = props => {\n const { loading } = useOrderForm()\n\n if (loading) {\n return <Loading />\n }\n\n return <Shipping {...props}>{props.children}</Shipping>\n}\n\nexport default ShippingWithLoading\n\n```"
}
] |
code_shipping-calculator_e2e01c75
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/styles.css from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```css\n:global .vtex-input__prefix {\n padding-right: 0.25rem;\n}\n\n```"
}
] |
code_shipping-calculator_3107c162
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/ShippingCalculator.tsx from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React, { useState } from 'react'\nimport { OrderShipping } from 'vtex.order-shipping'\nimport { ShippingForm } from 'vtex.checkout-shipping'\nimport { FormattedMessage } from 'react-intl'\nimport { ButtonPlain } from 'vtex.styleguide'\n\nconst { useOrderShipping } = OrderShipping\n\nconst ShippingCalculator: React.VFC = () => {\n const { selectedAddress } = useOrderShipping()\n const shouldInitiallyShowShippingEstimate = !!selectedAddress?.postalCode\n\n const [showShippingEstimate, setShowShippingEstimate] = useState(\n shouldInitiallyShowShippingEstimate\n )\n\n if (!showShippingEstimate) {\n return (\n <div>\n <ButtonPlain\n id=\"view-delivery-options\"\n onClick={() => setShowShippingEstimate(true)}\n >\n <FormattedMessage id=\"store/shipping-calculator.viewDeliveryOptions\" />\n </ButtonPlain>\n </div>\n )\n }\n\n return <ShippingForm />\n}\n\nexport default ShippingCalculator\n\n```"
}
] |
code_shipping-calculator_2d5ba3aa
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/package.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"version\": \"0.13.0\",\n \"scripts\": {\n \"test\": \"vtex-test-tools test\",\n \"lint\": \"tsc --noEmit && eslint --ext ts,tsx .\"\n },\n \"dependencies\": {\n \"@vtex/css-handles\": \"^1.0.0\",\n \"classnames\": \"^2.2.6\",\n \"prop-types\": \"^15.7.2\",\n \"ramda\": \"^0.26.1\",\n \"react\": \"^16.8.3\",\n \"react-dom\": \"^16.8.3\",\n \"react-intl\": \"3.9.1\"\n },\n \"devDependencies\": {\n \"@apollo/react-testing\": \"^3.1.3\",\n \"@types/classnames\": \"^2.2.7\",\n \"@types/graphql\": \"^14.2.0\",\n \"@types/jest\": \"^24.0.11\",\n \"@types/node\": \"^11.13.0\",\n \"@types/prop-types\": \"^15.7.0\",\n \"@types/ramda\": \"^0.26.5\",\n \"@types/react\": \"^16.9.53\",\n \"@types/react-intl\": \"^2.3.17\",\n \"@vtex/country-codes\": \"^1.0.2\",\n \"@vtex/styleguide\": \"^9.95.0\",\n \"@vtex/test-tools\": \"^3.3.2\",\n \"apollo-client\": \"^2.5.1\",\n \"typescript\": \"3.9.7\",\n \"vtex.address-context\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.address-context@0.6.1/public/@types/vtex.address-context\",\n \"vtex.checkout-components\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.checkout-components@0.5.1/public/@types/vtex.checkout-components\",\n \"vtex.checkout-shipping\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.checkout-shipping@0.7.1/public/@types/vtex.checkout-shipping\",\n \"vtex.country-codes\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.country-codes@2.0.1/public/_types/react\",\n \"vtex.formatted-price\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.formatted-price@0.4.0/public/@types/vtex.formatted-price\",\n \"vtex.native-types\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.native-types@0.7.5/public/@types/vtex.native-types\",\n \"vtex.order-manager\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.order-manager@0.9.0/public/@types/vtex.order-manager\",\n \"vtex.order-shipping\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.order-shipping@0.7.0/public/@types/vtex.order-shipping\",\n \"vtex.place-components\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.place-components@0.14.0/public/@types/vtex.place-components\",\n \"vtex.render-runtime\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.render-runtime@8.126.11/public/@types/vtex.render-runtime\",\n \"vtex.shipping-estimate-translator\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.shipping-estimate-translator@2.2.2/public/@types/vtex.shipping-estimate-translator\",\n \"vtex.styleguide\": \"http://vtex.vtexassets.com/_v/public/typings/v1/vtex.styleguide@9.135.2/public/@types/vtex.styleguide\"\n }\n}\n\n```"
}
] |
code_shipping-calculator_91c462ee
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/store/contentSchemas.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"definitions\": {\n \"ShippingCalculator\": {\n \"properties\": {\n \"title\": {\n \"title\": \"admin/editor.shipping-calculator.title\",\n \"$ref\": \"app:vtex.native-types#/definitions/text\",\n \"default\": \"store/shipping-calculator.delivery\"\n }\n }\n }\n }\n}\n\n```"
}
] |
code_shipping-calculator_bf0bd9e1
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/store/blocks.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"shipping-calculator\": {\n \"children\": [\"estimate-shipping\"]\n }\n}\n\n```"
}
] |
code_shipping-calculator_ed648b1c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/store/interfaces.json from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"shipping-calculator\": {\n \"component\": \"Shipping\",\n \"allowed\": [\"estimate-shipping\"],\n \"composition\": \"children\",\n \"content\": {\n \"$ref\": \"#/definitions/ShippingCalculator\"\n },\n \"preview\": {\n \"type\": \"box\",\n \"height\": 30,\n \"width\": 200,\n \"options\": {\n \"padding\": 0\n }\n }\n },\n \"estimate-shipping\": {\n \"component\": \"ShippingCalculator\"\n }\n}\n\n```"
}
] |
code_shipping-calculator_89dcdd72
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/typings/vtex.render-runtime.d.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\n/* Typings for `render-runtime` */\ndeclare module 'vtex.render-runtime' {\n import { Component, ComponentType, ReactElement, ReactType } from 'react'\n\n export interface NavigationOptions {\n page: string\n params?: any\n }\n\n export interface RenderContextProps {\n runtime: {\n navigate: (options: NavigationOptions) => void\n }\n }\n\n interface ExtensionPointProps {\n id: string\n [key: string]: any\n }\n\n export const ExtensionPoint: ComponentType<ExtensionPointProps>\n\n interface ChildBlockProps {\n id: string\n }\n\n export const ChildBlock: ComponentType<ChildBlockProps>\n export const useChildBlock = function({ id: string }): object {}\n\n export const Helmet: ReactElement\n export const Link: ReactType\n export const NoSSR: ReactElement\n export const RenderContextConsumer: ReactElement\n export const canUseDOM: boolean\n export const withRuntimeContext: <TOriginalProps extends {}>(\n Component: ComponentType<TOriginalProps & RenderContextProps>\n ) => ComponentType<TOriginalProps>\n}\n\n```"
}
] |
code_shipping-calculator_b848bf49
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/typings/global.d.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ninterface Address {\n addressId: string\n addressQuery?: string\n addressType: string\n city?: string\n complement?: string\n country?: string\n geoCoordinates?: number[]\n neighborhood?: string\n number?: string\n postalCode?: string\n receiverName?: string\n reference?: string\n state?: string\n street?: string\n}\n\ninterface NewAddress {\n addressId?: string\n addressQuery?: string\n addressType?: string\n city?: string\n complement?: string\n country?: string\n geoCoordinates?: number[]\n neighborhood?: string\n number?: string\n postalCode?: string\n receiverName?: string\n reference?: string\n state?: string\n street?: string\n}\n\ninterface AddressWithValidation {\n addressId: AddressField\n addressQuery?: AddressField\n addressType: AddressField\n city?: AddressField\n complement?: AddressField\n country?: AddressField\n geoCoordinates?: AddressField\n neighborhood?: AddressField\n number?: AddressField\n postalCode?: AddressField\n receiverName?: AddressField\n reference?: AddressField\n state?: AddressField\n street?: AddressField\n}\n\ninterface AddressField {\n value: string | number[]\n valid: boolean | null\n}\n\ninterface DeliveryOption {\n id: string\n price: number\n estimate: string\n isSelected: boolean\n}\n\ninterface CheckoutAddress {\n addressType: string\n receiverName: string\n addressId: string\n postalCode: string\n city: string\n state: string\n country: string\n street: string\n number: string\n neighborhood: string\n complement: string\n reference: string | null\n geoCoordinates: number[]\n}\n\ninterface DeliveryOption {\n id: string\n price: number\n estimate: string\n isSelected: boolean\n}\n\n```"
}
] |
code_shipping-calculator_bcba1cfc
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/typings/css.d.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ndeclare module '*.css' {\n const css: any\n export default css\n}\n\n```"
}
] |
code_shipping-calculator_578e06a4
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/typings/graphql.d.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ndeclare module '*.graphql' {\n import { DocumentNode } from 'graphql'\n\n const value: DocumentNode\n export default value\n}\n\n```"
}
] |
code_shipping-calculator_eb54c370
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/typings/vtex.styleguide.d.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ndeclare module 'vtex.styleguide' {\n import { ComponentType } from 'react'\n\n export const Input: ComponentType<InputProps>\n\n interface InputProps {\n [key: string]: any\n }\n}\n\n```"
}
] |
code_shipping-calculator_0b95fe50
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/utils/gguid.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nlet gguid = 1\n\nexport default function getGGUID() {\n return (gguid++ * new Date().getTime() * -1).toString().replace('-', '')\n}\n\n```"
}
] |
code_shipping-calculator_4b8e96b0
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/utils/slugify.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport const slugify = (text: string) => {\n return text.toLowerCase().replace(/\\s+/g, '-')\n}\n\n```"
}
] |
code_shipping-calculator_3ec1a627
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/utils/address.ts from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nimport getGGUID from './gguid'\n\nexport function newAddress(address?: NewAddress) {\n return {\n addressId: address?.addressId ?? getGGUID(),\n addressType: address?.addressType ?? 'residential',\n city: address?.city ?? '',\n complement: address?.complement ?? '',\n country: address?.country ?? '',\n geoCoordinates: address?.geoCoordinates ?? [],\n neighborhood: address?.neighborhood ?? '',\n number: address?.number ?? '',\n postalCode: address?.postalCode ?? '',\n receiverName: address?.receiverName ?? '',\n reference: address?.reference ?? '',\n state: address?.state ?? '',\n street: address?.street ?? '',\n addressQuery: address?.addressQuery ?? '',\n }\n}\n\n```"
}
] |
code_shipping-calculator_577c03ab
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/components/DeliveryOptionsAvailability.tsx from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React, { FunctionComponent, Fragment } from 'react'\nimport { FormattedMessage } from 'react-intl'\nimport { Alert } from 'vtex.styleguide'\n\ninterface Props {\n numberOfItems: number\n numberOfUnavailableItems: number\n}\n\nconst DeliveryOptionsAvailability: FunctionComponent<Props> = ({\n numberOfItems,\n numberOfUnavailableItems,\n}) => {\n const allItemsUnavailable = numberOfUnavailableItems === numberOfItems\n return (\n <Fragment>\n {numberOfUnavailableItems > 0 && (\n <Alert type=\"warning\">\n {allItemsUnavailable ? (\n <FormattedMessage\n id=\"store/shipping-calculator.allItemsUnavailable\"\n values={{ numberOfUnavailableItems }}\n />\n ) : (\n <FormattedMessage\n id=\"store/shipping-calculator.unavailableItems\"\n values={{ numberOfUnavailableItems }}\n />\n )}\n </Alert>\n )}\n </Fragment>\n )\n}\n\nexport default DeliveryOptionsAvailability\n\n```"
}
] |
code_shipping-calculator_e69f6a89
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of shipping-calculator/react/__tests__/Shipping.test.tsx from the shipping-calculator VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport { render } from '@vtex/test-tools/react'\nimport React from 'react'\nimport { OrderShippingContext } from 'vtex.order-shipping/OrderShipping'\nimport { OrderFormContext } from 'vtex.order-manager/OrderForm'\n\nimport Shipping from '../Shipping'\nimport ShippingCalculator from '../ShippingCalculator'\n\ninterface InsertAddressResult {\n success: boolean\n orderForm: any\n}\n\ninterface Context {\n countries: string[]\n selectedAddress: Address\n insertAddress: (address: CheckoutAddress) => Promise<InsertAddressResult>\n deliveryOptions: DeliveryOption[]\n selectDeliveryOption: (option: string) => void\n}\n\nconst mockedAddress = {\n addressId: '1569522356558',\n addressType: 'residential',\n city: 'Rio de Janeiro',\n complement: '',\n country: 'BRA',\n neighborhood: 'Botafogo',\n number: '',\n postalCode: '22230-005',\n receiverName: '',\n reference: '',\n state: 'RJ',\n street: '',\n geoCoordinates: [],\n}\n\nconst mockedDeliveryOptions = [\n { id: 'Motoboy', price: 500, estimate: '8d', isSelected: false },\n { id: 'PAC', price: 1000, estimate: '5d', isSelected: true },\n { id: 'Expressa', price: 1000, estimate: '7d', isSelected: false },\n]\n\nconst contextInfo = {\n countries: ['BRA'],\n selectedAddress: mockedAddress,\n deliveryOptions: mockedDeliveryOptions,\n selectDeliveryOption: jest.fn(),\n insertAddress: jest.fn(),\n}\n\ndescribe('Shipping', () => {\n const renderComponent = (customProps: Context) => {\n const {\n countries,\n deliveryOptions,\n insertAddress,\n selectDeliveryOption,\n selectedAddress,\n } = customProps\n\n const wrapper = render(\n <OrderFormContext.Provider\n value={{\n loading: false,\n orderForm: { shipping: { selectedAddress, deliveryOptions } },\n }}\n >\n <OrderShippingContext.Provider\n value={{\n countries,\n selectedAddress,\n deliveryOptions,\n selectDeliveryOption,\n insertAddress,\n }}\n >\n <Shipping title=\"Title\">\n <ShippingCalculator />\n </Shipping>\n </OrderShippingContext.Provider>\n </OrderFormContext.Provider>\n )\n return wrapper\n }\n\n it('should be rendered', () => {\n const component = renderComponent(contextInfo)\n expect(component).toBeDefined()\n })\n\n it('should show postal code', () => {\n const { getByText } = renderComponent(contextInfo)\n expect(getByText(mockedAddress.postalCode)).toBeTruthy()\n })\n\n it('should show delivery options', () => {\n const { getByText } = renderComponent(contextInfo)\n expect(getByText(mockedDeliveryOptions[0].id)).toBeTruthy()\n })\n\n it('should show delivery button', () => {\n const { getByText } = renderComponent({\n ...contextInfo,\n selectedAddress: { addressId: '', addressType: '' },\n })\n expect(getByText('View delivery options')).toBeTruthy()\n })\n})\n\n```"
}
] |
code_course-template_ac6244d2
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/config.json from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"title\": \"Template Course\",\n \"tagline\": \"Like a subtitle for your course\",\n \"description\": \"Description of your course\",\n \"languages\": [\"en\", \"pt\"],\n \"steps\": [\n {\n \"folder\": \"01-hello-world\",\n \"title\": { \"en\": \"First assignment\", \"pt\": \"Primeira tarefa\" },\n \"description\": {\n \"en\": \"Description for the Hello World step (used solely for Github's progress page)\",\n \"pt\": \"Descrição para o step de Hello World\"\n },\n \"challenge\": \"none\"\n },\n {\n \"folder\": \"02-writing-jsonc\",\n \"title\": {\n \"en\": \"On this step, we have tests that check if some JSONC files were correctly made\",\n \"pt\": \"Neste passo teremos testes para verificar se alguns arquivos JSONC foram corretamente criados\"\n },\n \"description\": { \"en\": \"Second description\", \"pt\": \"Segunda descrição\" },\n \"challenge\": \"tests\"\n },\n {\n \"folder\": \"03-writing-css\",\n \"title\": {\n \"en\": \"Here, we will get some CSS files and parse them, checking if the correct classes were declared\",\n \"pt\": \"Aqui, iremos parsear arquivos CSS submetidos e verificar se as classes foram corretamente criadas\"\n },\n \"description\": { \"en\": \"Third description\", \"pt\": \"Terceira descrição\" },\n \"challenge\": \"tests\"\n },\n {\n \"folder\": \"04-wrapping-up\",\n \"title\": {\n \"en\": \"Here you can set another title for this step\",\n \"pt\": \"Aqui você pode colocar outro título para seu step\"\n },\n \"description\": {\n \"en\": \"Every description is required for each step\",\n \"pt\": \"O campo descrição é obrigatório para todo step\"\n },\n \"challenge\": \"tests\"\n }\n ]\n}\n\n```"
}
] |
code_course-template_0ae6bab7
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/package.json from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"scripts\": {\n \"build\": \"tsc\",\n \"test\": \"yarn jest\"\n },\n \"dependencies\": {\n \"postcss\": \"^7.0.27\",\n \"ramda\": \"^0.27.0\",\n \"typescript\": \"3.7.3\"\n },\n \"devDependencies\": {\n \"@types/ramda\": \"^0.26.43\"\n }\n}\n\n```"
}
] |
code_course-template_a1483c04
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/global.d.ts from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nimport * as ramda from 'ramda'\n\nexport {} \n\ndeclare global {\n interface TestContext {\n getFile: (path: string) => Promise<string>\n parseCss: (content: string) => object\n parseJsonc: (content: string) => object\n ramda: typeof ramda\n [key: string]: any\n }\n\n interface TestFunctionParameters {\n ctx: TestContext\n }\n\n interface TestCase {\n tests: {\n description: string\n failMsg: string\n test: (param: TestFunctionParameters) => Promise<boolean> | boolean\n }[]\n }\n}\n\n```"
}
] |
code_course-template_e1261047
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/template/manifest.json from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"vendor\": \"vtex\",\n \"name\": \"change-me-course\",\n \"version\": \"0.1.0\",\n \"title\": \"Change me Course\",\n \"description\": \"\",\n \"defaultLocale\": \"en-US\",\n \"builders\": {\n \"store\": \"0.x\"\n },\n \"dependencies\": {\n \"vtex.store\": \"2.x\",\n \"vtex.rich-text\": \"0.x\"\n },\n \"$schema\": \"https://raw.githubusercontent.com/vtex/node-vtex-api/master/gen/manifest.schema\"\n}\n\n```"
}
] |
code_course-template_2830839c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/template/store/routes.json from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store.custom#change-me\": {\n \"path\": \"/change-me-course\"\n }\n}\n\n```"
}
] |
code_course-template_22c7e3a1
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/template/store/blocks/change-me.jsonc from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"store.custom#tab-layout\": {\n \"children\": [\n \"rich-text#foo\"\n ]\n },\n \"rich-text#foo\": {\n \"props\": {\n \"text\": \"iaew boy\"\n }\n }\n}\n\n```"
}
] |
code_course-template_b229185b
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/steps/03-writing-css/index.ts from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport default {\n tests: [\n {\n description: 'First test of SECOND step',\n failMsg: 'You can also throw custom error messages. This will be the default message sent.',\n test: async({ ctx }) => {\n const pdp = await ctx.getFile('store/blocks/product.jsonc') \n return !!pdp\n }\n }\n ]\n} as TestCase\n\n```"
}
] |
code_course-template_09e3bcb3
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/steps/02-writing-jsonc/index.ts from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport default {\n tests: [\n {\n description: 'First TEeT of this step',\n failMsg: 'You can also throw custom error messages. This will be the default message sent.',\n test: async ({ ctx: { getFile } }) => {\n const pdp = await getFile('store/blocks/product.jsonc')\n return !!pdp\n },\n },\n ],\n} as TestCase\n\n```"
}
] |
code_course-template_3d0669cc
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of course-template/course/steps/04-wrapping-up/index.ts from the course-template VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport default {\n tests: [\n {\n description: 'Test for the last step',\n failMsg: 'You can also throw custom error messages. This will be the default message sent.',\n test: async ({ ctx }) => {\n const pdp = await ctx.getFile('store/blocks/product.jsonc')\n return !!pdp\n },\n },\n ],\n} as TestCase\n\n```"
}
] |
code_release-notes_3088489d
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n> ↪️ **CONTENT MIGRATION NOTE**\n>\n> The content of this repository has been **migrated to [dev-portal-content](https://github.com/vtexdocs/dev-portal-content).**\n>\n> We apologize for any inconvenience this may cause and thank you for your understanding.\n\n```"
}
] |
code_release-notes_fc42094b
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-01/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - January 2020\ndescription: \"See what is new in VTEX IO January 2020\"\ndate: \"2020-02-10\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-01/README.md\"\n---\n\n# VTEX IO Release Notes - January 2020\n\nAnd we are back, ladies and gentlemen :clap:\n\nLong time no see... really missed you guys! I'm sure that you've missed us too, right? RIGHT :smirk:\n\n2019 was a special, intense and long year, full of learnings for each and every one of us, that's for sure. But the time has come to aim above and beyond to **greatness**. Therefore, make sure to keep up-to-date with the IO Release Notes! It's the only way to keep up with everything that we're dutifully preparing for you.\n\n2020, here we are. And here we go:\n\n## Features :rocket:\n\n- **Minicart v2** - A brand new Minicart is up and running, much more optimized and flexible that it's former version. For a look at the reasons why you'll want to migrate asap, check out the [documentation](https://vtex.io/docs/components/all/vtex.minicart/).\n\n- **Block's composition** - This one here is truly mind-blowing so listen closely: within a block's `children` array, you can now declare any block you choose. That's right! When setting a block as another's child, forget about the allowed blocks list. Declare whatever block you want. But remember: this only works for the `children` array. Blocks declared in the `blocks` array will remain limited to the allowed list of the block parent.\n\n- **Store Link app** - An app that allows you to create and display links that automatically consume context from other blocks. Sounds confusing? It is actually simple and amazing. Just give a look at the [Store Link](https://vtex.io/docs/components/all/vtex.store-link/) documentation.\n\n- **JivoChat** - Integrate your store with the JivoChat solution using the [JivoChat pixel app](https://vtex.io/docs/components/pixel/vtex.jivochat/), available now just a click away from you.\n\n- **Listrak** - More pixel apps to come! You are now also able to natively integrate with the [Listrak](https://vtex.io/docs/components/pixel/vtex.listrak-pixel/) solution.\n\n## Improvements :heavy_plus_sign:\n\n- **Site Editor** - Our beloved admin's Site Editor now allows you to configure some of the many [Shelf](https://vtex.io/docs/components/all/vtex.shelf/) (`maxItems`, `arrows`, `showTitle`, `titleText`, `minItemsPerPage`, `itemsPerPage` and `paginationDotsVisibility`) and [Slider Layout](https://vtex.io/docs/components/all/vtex.slider-layout/) (`navigationStep`, `itemsPerPage` and `autoplay`) props.\n\n- **Search Results Filters** - The new `facetsBehavior` prop only allows you to display filters with actual search results in the [Search Result](https://vtex.io/docs/components/all/vtex.search-result/) page. No more misleadings. Yay!\n\n- **Product Summary image** - Choose which product image will be shown in the [Product Summary Image](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-image) block thanks to the new `mainImageLabel` prop.\n\n- **CSS Handles** - More CSS Handles for several apps, among which: [Stack Layout](https://vtex.io/docs/components/all/vtex.stack-layout/), [Product Summary](), [Search Result](https://vtex.io/docs/components/all/vtex.search-result/), [Menu](https://vtex.io/docs/components/all/vtex.menu/), [Minicart](https://vtex.io/docs/components/all/vtex.minicart/), [Flex Layout](https://vtex.io/docs/components/all/vtex.flex-layout/)) and ALL [store icons](https://vtex.io/docs/components/all/vtex.store-icons/). We're seriously not kidding around when it comes to Handles... do not forget to check out each related documentation.\n\n- **SKU Selector** - Previously, the `showValueNameForImageVariation` prop did not serve every scenario it is was meant to because it only indicated a variation's value if it was an image type. It was replaced with a prop, namely the `showValueForVariation`, that encompasses even more scenarios, that is, it now indicates variation's value of all types (image and others!). Do not forget to give the [documentation](https://vtex.io/docs/components/all/vtex.store-components/sku-selector) a quick sneak peak to understand the prop's behavior.\n\n- **Product Summary SKU Selector** - The possibility to add a slider in the [Product Summary SKU Selector](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-sku-selector) to make user navigation easier has just become reality thanks to the new `displayMode` prop.\n\n## Notable bug fixes :bug:\n\n- **Search Results ordering** - It's always a good idea to improve the Search Results page. Now, sorting products by \"Relevance\" takes the [score field](https://help.vtex.com/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcae) value set in the admin's Catalog into consideration.\n\n- **SKU Selector ordering** - We're really putting our house in order in 2020: the SKU Selector now respects the position given to [SKU specifications](https://help.vtex.com/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#sku-specifications) values defined in the admin's catalog, displaying everything according to the retailer's order preference.\n\n- **Product Impression event** - Previously, Product Impression events faced a problem: whenever the Shelf was hovered over, the event triggered the store’s Google Analytics informing that all Shelf products had been seen by the user, even those that were hidden by the SKU Selector’s slider. This is now changed: only products that are in fact displayed are sent by the event.\n\n```"
}
] |
code_release-notes_db2528aa
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-06/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - June 2020\ndescription: \"See what is new in VTEX IO for June 2020\"\ndate: \"2020-07-16\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-06/README.md\"\n---\n\n# VTEX IO Release Notes - June 2020\n\nWelcome to the VTEX IO Release Notes for June 2020, team! \n\nI know home office can be ~~extremely~~ a little bit tiring, but I do hope you will be able to set some time aside from your busy workweek to **catch up with VTEX IO latest news**. \n\nNotice: i'm not saying this only because I'm the one writing the VTEX IO release notes, you know... it's actually because the past month of June really brought us some goodies worth looking at asap, such as:\n\n- :rocket: The new Sitemap app\n- :heavy_plus_sign: The 404 pages improvement\n- :bug: The Clear button (from mobile filter sidebar) bug fix\n\nCheck out the last month's key changes below:\n\n## Features :rocket:\n\n- **Sitemap** - One long awaited tool for SEO is finally out of the oven: manage your website's sitemap file from now on using the new [VTEX IO Sitemap app](https://vtex.io/docs/components/functional/vtex.store-sitemap/). \n\n- **Image zooming in a modal** - Open a modal for product image zooming whenever the Product Images component (`product-image` block) is clicked on. The instructions for setting up this new feature are available in the Advanced configuration section of the [Product Image block documentation](https://vtex.io/docs/components/all/vtex.store-components/productimages/).\n\n- **Confirmation modal on Minicart** - Using the [Modal Layout app](https://vtex.io/docs/components/all/vtex.modal-layout/), you can now display a confirmation modal when users decide to remove an item from the minicart. Learn how to configure the confirmation modal in your store by accessing the [Creating modals using icons](https://vtex.io/docs/recipes/templates/creating-modals-using-icons/) documentation.\n\n- **VTEX IO Service Worker management** - Activate and deactivate the native VTEX IO service worker according to your store needs! This feature is a must if you are dealing with a third solution service worker. For more info, access the [Managing VTEX IO native service worker](https://vtex.io/docs/recipes/store-management/deactivating-the-vtex-io-native-service-worker/) documentation. \n\n## Improvements :heavy_plus_sign:\n\n- **404 pages** - The 404 pages feature was remodeled. It was already possible to natively enable 404 pages for nonexistent product pages and for URLs that have more than one invalid segment. But in addition to that, you can now also allow 404 pages when URLs have a single invalid path segment. Cheers to that! Learn more about this setup in the [Enabling 404 pages](https://vtex.io/docs/recipes/store-management/enabling-404-pages/) documentation. \n\n- **Checkbox buttons customization** - New CSS Handles were added to the VTEX Styleguide in order to simplify the Checkbox button customization, such as those ones used in filters from the search results page, namely `vtex-checkbox__box-wrapper`, `vtex-checkbox__box`, and `vtex-checkbox__input`. For further details, do not forget to check out the [VTEX Styleguide](https://styleguide.vtex.com/). \n\n- **Price Range component customization** - A new CSS Handle called `vtex-slider__base-internal` was also added to the VTEX Styleguide in order to simplify the customization of the Price Range component, rendered on the Search Result page. As previously recommended, you can access the [VTEX Styleguide](https://styleguide.vtex.com/) for more info. \n\n- **Search bar in modals** - Displaying a search bar in a modal using the [Modal Layout app](https://vtex.io/docs/components/all/vtex.modal-layout/) and the [Search Result](https://vtex.io/docs/components/all/vtex.search-result/) block `search-bar` was already possible. Now, however, the modal is immediately closed when a search is performed by users, enhancing their navigation experience.\n\n- **Product Specifications customization** - It became possible to apply CSS classes for each product specification displayed on the interface, allowing for their independent customization. This marvel of a release is all thanks to the way CSS Handles (used by the [Product Specifications](https://vtex.io/docs/components/all/vtex.store-components/productspecifications/) block) currently behave when inspected. \n\n- **Product Summary Name heading tags** - Forget about when a single heading tag was mandatory: using the new `tag` prop, you can now choose which heading tag should be applied when rendering the Product Summary Name block. Don't forget to check out the [block documentation](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-name/). \n\n- **Add To Cart Button text label** - We really mean to empower our users: decide which text should be displayed on the Add To Cart Button using its new props `text` and `unavailableText`. For more, access the [Add To Cart Button documentation](https://vtex.io/docs/components/all/vtex.add-to-cart-button/). \n\n- **Add To Cart Button behavior** - One more for the Add To Cart Button: thanks to its new prop `onClickBehavior`, you can now set the button's behavior once it is clicked on, defining whether it will redirect users to the product page or directly add the given product to the minicart. Check out more in the [Add To Cart Button documentation](https://vtex.io/docs/components/all/vtex.add-to-cart-button/).\n\n*Still with us? We are just half way there! Hold on tight, because we still have some great improvements to show you:*\n\n- **Product Summary Buy Button behavior** - We're really improving some buttons here, aren't we? The `product-summary-buy-button` block, exported by the Product Summary app, has a new prop called `buyButtonBehavior` that defines the button's behavior when clicked on. Understand which behaviors are accepted by accessing the [Product Summary Buy Button documentation](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-buy-button/).\n\n- **Open Graph meta tags** - Open Graph meta tags (used by Facebook) are now available in the `store.home`, `store.product`, and `store.search` templates (respectively home, product, and search result pages). These tags are extremely useful when these pages are shared on Facebook, since they're used to display rich previews to users. \n\n- **CSS Handles for Search Result** - A VTEX IO release notes is not a proper one if it does not include new CSS Handles. `filterBreadcrumbsItem` and `filterBreadcrumbsItemName` were added to the [Search Result app](https://vtex.io/docs/components/all/vtex.search-result/), allowing for the customization of filter breadcrumbs on mobile devices. \n\n- **CSS handles for Search Bar** - Another CSS Handles release to make you smile: the [Search Bar block](https://vtex.io/docs/components/all/vtex.store-components/searchbar/), exported by the [Store Components app](https://vtex.io/docs/components/all/vtex.store-components@3.119.6/), gained new handles responsible for customizing the search bar component specifically when it is opened and/or filled out by users. \n\n- **Quantity badge behavior on Minicart** - The `minicart.v2` block, part of the Minicart app (v2), received a new prop called `itemCountMode`. This new prop is responsible for defining the quantity badge's behavior when displaying the number of items added to the Minicart. Understand which behaviors are accepted by accessing the [Minicart app documentation](https://vtex.io/docs/components/all/vtex.minicart/).\n\n- **Minicart icon** - Flexibility is what we aimed for this past month! Thanks to the new `MinicartIcon` prop, you can now change the Minicart icon (v2) by choosing from the icons exported by the [Store Icons app](https://vtex.io/docs/components/all/vtex.store-icons/). Check out the [Minicart documentation](https://vtex.io/docs/components/all/vtex.minicart/) in order to learn how to use this new prop. \n\n- **Progress bar on the search results page** - The `search-products-progress-bar` block, responsible for displaying a progress bar for product results on the search results page, can now be declared as a child of the `search-result` block from the previous version of the [Search Result app](https://vtex.io/docs/components/all/vtex.search-result/). Previously, it only could be declared as a child of the `search-result-layout` block pertaining to current version of the app. \n\n## Bug fixes :bug:\n\n- **[Clear button from mobile filter sidebar](https://github.com/vtex-apps/search-result/pull/376)** - The Filter sidebar's `Clear` button was not properly working on mobile devices, since it was not properly clearing filters applied by users. This behavior has been fixed and the button now clears every checked filter. \n\n- **[Assembly options selection](https://github.com/vtex-apps/product-customizer/pull/67)** - Previously, assembly options were only selected if the user clicked on the Radio button/checkbox. In order to improve user experience, assembly options are now duly selected whenever users select them (whether using the buttons or not). \n\n- **[Newsletter's email address field](https://github.com/vtex-apps/store-components/pull/790)** - Spaces unintentionally added to the [Newsletter](https://vtex.io/docs/components/all/vtex.store-components@3.119.6/newsletter/)'s email address field were invalidating user subscriptions. The component no longer accepts spaces in the field, thus improving user experience.\n\n- **[Search Result's custom query](https://github.com/vtex-apps/search-result/pull/359)** - The `search-result-layout.customQuery` block, exported by the [Search Result app](https://vtex.io/docs/components/all/vtex.search-result/) and responsible for performing custom queries to the Search API, was not properly working when declared in a column built by the [Flex Layout app](https://vtex.io/docs/components/all/vtex.flex-layout/). This unwanted behavior is now fixed. \n\n## Praises :sparkles:\n\nWe would not be able to deliver so many amazing results during this last month if it were not for the following outstanding contributors:\n\n- [BeatrizMiranda](https://github.com/BeatrizMiranda) _from ACCT_\n- [gustavopvasconcellos](https://github.com/gustavopvasconcellos) _from ACCT_\n- [ygorneves10](https://github.com/ygorneves10) _from Corebiz_\n- [igorpoubel](https://github.com/igorpoubel) _from Corebiz_\n\nThank you, team :muscle:\n\n```"
}
] |
code_release-notes_cc74c320
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-34/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 34/2019\ndescription: \"See what is new in VTEX IO Week 34/2019\"\ndate: \"2019-08-30\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-34/README.md\"\n---\n\n# VTEX IO Highlights - Week 34/2019\n\nHello, team!\n\nToday is the last working day of August :tada:\n\nIn order to celebrate the end of this endless month, check out the VTEX IO Release Notes for this week:\n\n> :bell: Keep up with VTEX IO release notes! Simply click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- [Toolbelt apps installation inspection](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-34/toolbelt-apps-installation-inspection.md) - Automatically check whether route conflicts can occur in your workspace as a result of installing an app.\n- [`ProductSummaryBrand` component](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-34/ProductSummaryBrand-component.md) - Render brand data with your own customizations in your Shelf component.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-34/platform-performance.md) - Understand last week's VTEX IO performance improvement key points.\n- [Shelf in mobile mode](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-34/shelf-in-mobile-mode.md) - Partially display products in Shelf component without breaking the page layout.\n\n### Notable bug fixes :bug:\n\n- [CSS Filter Navigator Handles](https://github.com/vtex-apps/search-result/pull/223) - At long last, numerous `filter-navigator.v2` elements got new CSS handles.\n- [Telemarketing user profile](https://github.com/vtex-apps/telemarketing/pull/53) - Telemarketing user issues were fixed, such as the UI, login/logout failure and the orderForm not being updated with the customer's data.\n\n```"
}
] |
code_release-notes_d723b013
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-08/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - August 2020\ndescription: \"See what is new in VTEX IO for August 2020\"\ndate: \"2020-09-18\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-08/README.md\"\n---\n\n# VTEX IO Release Notes - August 2020\n\nIt may make a delayed entrance, but it never fails: it's finally here guys :pray:\n\nDid you know that August is called the month of chagrin by some in Brazil? Nonsense.... VTEX IO is here to prove them wrong with this month's release notes. \n\nA lot of freshly baked wonder-cakes are finally out of our development oven, among which:\n\n- 🚀 The new Disclosure Layout app\n- ➕ Change in the app deploying time\n- ❌ Product Specifications block deprecation\n\nWonderful right? And it is not just because I wrote everything here... this month's release notes is so blissful that is would change anyone's mood. Have a closer look:\n\n## Features 🚀\n\n- **Disclosure Layout app** - The Disclosure Layout app is finally among us! The new layout app is responsible for creating a layout structure based on disclosure triggers, as shown below. For more details on the new app, access the [Disclosure Layout documentation](https://vtex.io/docs/components/layout-blocks/vtex.disclosure-layout/).\n\n\n\n- **Product Highlights app** - The Product Highlights app is here to allow you to display highlight badges on products according to the collection or promotion they are linked to. To learn how to configure it in your store, check out the [Product Highlights app documentation](https://vtex.io/docs/components/all/vtex.product-highlights/).\n\n\n\n- **Product Specifications app** - Aiming to bring you more flexibility when using the Product Specifications component, our product team developed the Product Specifications app, replacing the former [Product Specifications block](https://github.com/vtex-apps/store-components/blob/master/docs/ProductSpecifications.md) exported by the [Store Components app](https://vtex.io/docs/app/vtex.store-components). Its setup is just a few clicks away: check out the new [Product Specifications app documentation](https://vtex.io/docs/components/all/vtex.product-specifications/)!\n\n\n\n- **Product Price block for seller name** - A new block responsible for displaying the seller name next to the product price is among us! Learn how to configure the `product-seller-name` block in your store by accessing the [Product Prices app documentation](https://vtex.io/docs/components/all/vtex.product-price/).\n\n\n\n## Improvements ➕\n\n- **Slider Layout's elements positioning** - The Slider Layout has gained a new prop called `centerMode`, which is responsible for defining how slider elements are positioned on the screen for each device. One of its possible values is `center` which allows you to display your slider element in a centered way to your users, as shown below. This improvement is extremely useful for Shelves and other components that use the Slider Layout for rendering product data. \n\n\n\n- **Filters display on Search Result page** - Thanks to the new `openFiltersMode` prop, you can now define how many filters a user can concomitantly open on the Filter Navigator component. For more details, access the [Search Result app documentation](https://vtex.io/docs/components/all/vtex.search-result/)!\n\n\n\n*Note that only one filter can be opened at any time. In the example above, the prop `openFiltersMode` is declared as `one`.*\n\n- **Bazaar Voice info in Google structured data** - From now on, user review data fetched by the Bazaar Voice app is considered in Google's structured data, used to understand and gather information about the content of the store's page. This improvement is extremely useful for SEO purposes since google will now be able to effectively fetch product reviews and display them on search result pages.\n\n\n\n- **Markdown interpretation by Assets Builder** - The [Assets Builder](https://vtex.io/docs/recipes/development/using-the-assets-builder) now supports assets whose URLs are built using markdown. This improvement is extremely useful and relevant since block props use the markdown structure to declare media on components.\n\n- **App deploying time** - Aiming to strengthen the security of our development process, published apps will now have to wait 7 minutes until they become ready to be deployed. Note the following: if this timing is not respected, an `Invalid state transition` error will be received from Toolbelt. For more on this process, check out the [Publishing an app](https://vtex.io/docs/recipes/development/publishing-an-app) documentation.\n\n- **`pageInfo` event on search results page** - Retailers can now benefit from the new search results page event: the `pageInfo`. Your store's new taggable event is triggered whenever the search results page content is changed due to user interaction, namely: selecting new filters, reordering the results, and clicking on the `Show More` button.\n\n- **EAN in Google Analytics events** - The EAN (product identifier) data is now included in the `addToCart` event. In practice, this means that the VTEX Store Framework now provides EAN data to Google Analytics events, allowing for a deeper analysis and extra integrations.\n\n- **Dynamic content on Slider Layout** - The Slider Layout has gained full dynamic content support! Previously, the component couldn't behave as expected with a dynamic number of slides i.e. when slides were added and removed according to user interaction (as in the case with product-comparison components). The Slider Layout is now adapted to always work as it is configured, regardless of its new content.\n\n- **Minicart v2 automatic display** - A trigger responsible for automatically opening the Minicart v2 on the interface can now be set by using any desired store event and the block's new `customPixelEventId` and `customPixelEventName` props! A long-awaited scenario, in which this new release is extremely useful, is to automatically open the Minicart component whenever the `Add To Cart button` is clicked on by users. Brace yourselves because the wait has finally come to an end: to prettify this release, the `add-to-cart-button` block has also gained a new prop called `customPixelEventId` to broadcast an event of its own when it is clicked on. In practice, this means that you can now set up both `add-to-cart-button` and `minicart.v2` blocks to configure this behavior in your store, displaying the options to move to checkout or just keep shopping to your users.\n\n*Hold on tight, my friend! Some amazing improvements related to store customization still await you:*\n\n- **Image's non-active dots customization [CSS Handle]** - Previously, we had no CSS handles that would enable users to select and customize non-active dots in the `product-images` block (from [Store Components app](https://vtex.io/docs/app/vtex.store-components/)). Thanks to the new `swiperBullet` and `swiperBullet--active` CSS Handles, an image's non-active dots can now be selected and customized. For more on this, access the [Product Images block documentation](https://vtex.io/docs/components/all/vtex.store-components/product-images/) and our documentation on [Using CSS Handles for store customization](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization/).\n\n\n\n*In the image above only the first image dot, which was currently selected (or active), had both `vtex-store-components-3-x-swiperBullet` and `vtex-store-components-3-x-swiperBullet--active` CSS classes. The second image dot, which was not active, did not have any CSS class which basically meant that users could not select it for customization.*\n\n- **Product Specifications block customization [CSS Handles]** - New CSS Handles, namely `specificationsTableRow`, `specificationsTableHead`, and `specificationsTableBody`, were added to the [Product Specifications block](https://github.com/vtex-apps/store-components/blob/master/docs/ProductSpecifications.md), exported by the [Store Components app](https://vtex.io/docs/app/vtex.store-components/), in order to grant you more flexibility while customizing the component's elements.\n\n\n\n***Caution**: As previously informed, the Product Specifications block was deprecated and replaced with the Product Specifications app. This release only applies to the former.*\n\n- **Drawer overlay customization [CSS Handles]** - The Drawer app has gained two new CSS Handles, namely `overlay` and `overlay--visible`, responsible for allowing retailers to customize the overlay structure used by the mobile component. For further details, access this [practical example recorded on loom](https://www.loom.com/share/d4da3624507e464281caae057496a426), as well as the [Drawer app documentation](https://vtex.io/docs/components/all/vtex.store-drawer/).\n\n - **`nth-child` CSS Selector with step size** - `:nth-child` selectors with step size, such as `:nth-child(2n)` are now allowed when customizing your store with CSS! For more on customizing your store with CSS and HTML selectors, access [Using CSS Handles for store customization](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization/#best-practices).\n \n## Deprecations ❌\n\n- **Product Specifications block** - The [Product Specification block](https://github.com/vtex-apps/store-components/blob/master/docs/ProductSpecifications.md), pertaining to the [Store Components app](https://vtex.io/docs/app/vtex.store-components/) was deprecated. Although support for this block is still provided, we strongly recommend you to update your store theme with the [**Product Specifications app**](https://vtex.io/docs/components/all/vtex.product-specifications@1.0.1/) in order to benefit from greater flexibility and to keep up with the component's evolution.\n\n## Bug fixes 🐛\n\n- **[Sum of installments without interest on search results page](https://github.com/vtex-apps/search-resolver/pull/84)** - Previously, the search query was presenting price errors when displaying product data on the search results page. As shown in the image below, the sum of installments without interest was higher than the product price itself, leading to a poor and frustrating user experience. The search query for this page was fixed and the bug removed, meaning that the sum of installments without interest is now displayed mathematically correct on search results pages as well as on the product details page.\n\n\n\n## Praises ✨\n\nWe would not be able to deliver so many amazing results during this last month if it were not for the following outstanding contributors:\n\n- [BeatrizMiranda](https://github.com/BeatrizMiranda) *from ACCT*\n- [Lucas Pacheco](https://github.com/lucaspacheco-acct) *from ACCT*\n- [Marcos Ewbank](https://github.com/marcosewbank) *from ACCT*\n- [Gabriel Carafizi](https://github.com/carafizi1) *from ACCT*\n- [Gustavo Vasconcellos](https://github.com/gustavopvasconcellos) *from ACCT*\n- [Jayendra](https://github.com/Jayendra88) *from Clouda*\n\nThank you, team! 💪\n\n\n\n```"
}
] |
code_release-notes_94b7661c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-09/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - September 2020\ndescription: \"See what is new in VTEX IO for September 2020\"\ndate: \"2020-10-23\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-09/README.md\"\n---\n\n# VTEX IO Release Notes - September 2020\n\nJust in time: **the VTEX IO Release Notes for September 2020 is finally *among us***!\n\nThat being said, your task list from now on consists of:\n\n- Read our hot-off-the-press news.\n- Implement the latest and best configs in your store.\n- Spread the word to your crewmates about the newest VTEX IO Release Notes.\n\nEasy-peasy... and let me tell you this: our team has prepared so many delightful releases that I'm 100% sure that the above tasks will be done even before tiredness gets to you! No sabotage is allowed!\n\nShall we?\n\n## Features :rocket:\n\n- **Store Video app** - The Store Video app has arrived, allowing you to display video assets on your store pages with divine features such as auto-play, loop, and mute. It gets even better: the app also supports YouTube, Vimeo, and other third-party players! What are you waiting for? Check out now the [documentation](https://vtex.io/docs/components/content-blocks/vtex.store-video/)!\n\n\n\n- **Product SKU Attributes block** - The [Store Component app](https://vtex.io/docs/components/content-blocks/vtex.store-components/)'s brand new block is here to allow you to effortlessly display product SKU attributes. Learn more about it in the [Product SKU attributes documentation](https://vtex.io/docs/components/content-blocks/vtex.store-components/productskuattributes/)!\n\n\n\n- **Facebook Domain Verification app** - The Facebook Domain Verification adds a meta-tag containing the Facebook verification code to your homepage `<head>`, which is used by Facebook for checking your website's ownership. The new app is more than ready to be installed: access its documentation [here](https://vtex.io/docs/components/pixel/vtex.facebook-domain-verification/)!\n\n- **Auto-complete for `product-context` properties** - The TypeScript types of the `vtex.product-context` app are working! Now, if you develop a React app that depends on them, you might run `vtex setup --typings` to have auto-complete and other juicy features that types provide. \n\n## Improvements :heavy_plus_sign:\n\n- **Performance optimization** - If there is one thing that everyone dreams about, it's performance optimization! With that in mind, the VTEX IO team has prepared a bunch of new configs for you, such as *partial fetching of facets on the search results page* and *CSS concatenation*. The best part is that they are just a couple of clicks away: check out now the documentation on [improving your store's performance](https://vtex.io/docs/recipes/store-management/improving-your-stores-performance/) and apply our best practices in your store!\n\n\n\n- **Repetitive purchase of products** - Before this release, adding the same product to the [Minicart v2](https://vtex.io/docs/components/content-blocks/vtex.minicart/) multiple times was kind of a big challenge for store users. Due to the `Item already on cart` error message, displayed whenever the `Add to cart` button was clicked on more than once, users were being blocked from having a smooth shopping experience. Good thing that loss in sales is not something we condone, nor want. Therefore, users are now able to click on the [Add to cart button](https://vtex.io/docs/components/content-blocks/vtex.add-to-cart-button/) as many times as desired! Cheers to that!\n\n\n\n- **Filtering payment methods in the search query** - Thanks to two new props, namely `includedPaymentSystems` and `excludedPaymentSystems`, it finally became possible to define which payment methods should and should not be taken into account in the search query when displaying the installment options to your store users. Access the [Search Results app documentation](https://vtex.io/docs/components/content-blocks/vtex.search-result/) now and learn how to set these props up in your search results page!\n\n- **Power Review app internationalization** - The [Power Review app](https://vtex.io/docs/components/pixel/vtex.powerreviews/) now works properly with international stores! When globalizing your brand, you no longer need to worry about user reviews in different languages: from this release onward, reviews are automatically fetched, translated, and displayed according to the store locale set by users.\n\n- **Radio and Radiogroup customization** - The Radio and Radiogroup [VTEX Styleguide](https://styleguide.vtex.com/#/Introduction) components have gained these new CSS Handles to call their own: `vtex-radiogroup__fieldset`, `vtex-radiogroup__legend`, `vtex-radiogroup__label`, `vtex-radiogroup__radioContainer`, and `vtex-radiogroup__error`, thus allowing you to customize several store components that are built using them, including [Store Form](https://vtex.io/docs/components/content-blocks/vtex.store-form/) and [Newsletter](https://vtex.io/docs/components/content-blocks/vtex.store-components/newsletter).\n\n- **Sales channel parameter in the `productsByIdentifier` query** - A new parameter was added to the [`productsByIdentifier` search query](https://github.com/vtex-apps/search-graphql/blob/master/graphql/schema.graphql#L216), allowing your custom components to fetch and display products according to the desired sales channel.\n\n- **Item ID as product identifier** - From now on, the [Product Identifier app](https://vtex.io/docs/components/content-blocks/vtex.product-identifier/) also accepts item IDs as product identifiers. Before this release, only Product Reference, Product ID, SKU EAN, and SKU Reference ID were accepted as valid to be displayed on the component.\n\n\n\n## Bug fixes :bug:\n\n- [Title attribute missing in image components](https://github.com/vtex-apps/store-image/pull/24) - The title attribute was nowhere to be found in store images. Poor little guy! It was linked to the incorrect HTML element when components were rendered - `a` instead of `img`. This behavior is now fixed and the title attribute can be properly found and tracked.\n\n- [SKU Selector frozen on slider component](https://github.com/vtex-apps/slider-layout/pull/46) - The SKU Selector had its product data frozen when rendered on slider components. In this previous and ugly scenario, users could only update the data displayed either when scrolling the page or when changing the slide currently hovered on. The good thing is that we are close to summer in Brazil and the SKU Selector was defrosted just in time: it is now working as expected!\n\n## Docs :page_facing_up:\n\nDocumentation is **key**! Check out our out-of-the-oven docs below : \n\n### Tracks\n\n- [Desenvolva componentes usando VTEX IO e React](https://vtex.io/docs/getting-started/desenvolva-componentes-usando-vtex-io-e-react/1/) (*Develop components using VTEX IO and React*) - Currently only available in Portuguese!\n\n### Recipes\n\n- [Using events to trigger side effects on store components](https://vtex.io/docs/recipes/templates/using-events-to-trigger-side-effects-on-store-components/)\n- [Cross-border store content internationalization](https://vtex.io/docs/recipes/store-management/cross-border-stores-content-internationalization/)\n- [Managing landing pages in cross-border stores](https://vtex.io/docs/recipes/store-management/managing-landing-pages-in-cross-border-stores/)\n- [Creating robots files for cross-border stores](https://vtex.io/docs/recipes/store-management/creating-robots-files-for-cross-border-stores/)\n- [Checking your store’s binding ID](https://vtex.io/docs/recipes/store-management/checking-your-store-binding-id/)\n- [Multi-language stores](https://vtex.io/docs/recipes/store-management/multi-language-stores/)\n- [Migrating CMS settings after a theme major update](https://vtex.io/docs/recipes/development/migrating-CMS-settings-after-major-update/)\n- [Running IO scripts in any VTEX store](https://vtex.io/docs/recipes/development/running-IO-scripts-in-any-VTEX-store/)\n\n### Concepts\n\n- [Billing Option](https://vtex.io/docs/concepts/billing-options/)\n- [Cross-border stores](https://vtex.io/docs/concepts/cross-border-stores/)\n- [Slots](https://vtex.io/docs/concepts/slots/)\n\n## Praises :sparkles:\n\nWe would not be able to deliver so many amazing results during this last month if it were not for the following outstanding contributors:\n\n- [Marcos Ewbank](https://github.com/marcosewbank) *from ACCT*\n- [Raissa Campos](https://github.com/raissacmp) *from ACCT*\n- [Lucas Pacheco](https://github.com/lucaspacheco-acct) *from ACCT*\n- [Gabriel Carafizi](https://github.com/carafizi1) *from ACCT*\n- [Erislandio](https://github.com/Erislandio) *from ACCT*\n\n\n\n\n```"
}
] |
code_release-notes_1178745c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-35/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 35/2019\ndescription: \"See what is new in VTEX IO Week 35/2019\"\ndate: \"2019-09-06\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-35/README.md\"\n---\n\n# VTEX IO Highlights - Week 35/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nWe're extremely happy to have achieved 10 straight weeks of VTEX IO Release Notes 🎉 We hope that you're excited as well!\n\nUnfortunately, this week's Release Notes size does not do justice to our impish glee with this achievement. This one comes in a mini format since our team is laser focused on improving the platform's performance.\n\nCheck out what were the key changes for the last week:\n\n> :bell: Keep up with VTEX IO release notes! Simply click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- [Google Search Box script](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-35/google-search-box-script.md) - Effortlessly display a store's internal search box during Google searches and watch how page access soars.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-35/platform-performance.md) - Understand last week's VTEX IO key performance improvement points.\n\n### Notable bug fixes :bug:\n\n- [Shelf `itemsPerPage` limit](https://github.com/vtex-apps/shelf/pull/176) - The Shelf component had a bug that limited the number of items it displayed to 5. Now, whatever number of items the `itemsPerPage` decides is duly displayed.\n- [RelatedShelf component](https://github.com/vtex-apps/shelf/pull/179) - The RelatedShelf no longer displays a maximum quantity of products due to not being able to properly identify if it's rendering for mobile or not.\n\n```"
}
] |
code_release-notes_acf1353c
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-07/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - July 2020\ndescription: \"See what is new in VTEX IO for July 2020\"\ndate: \"2020-08-17\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-07/README.md\"\n---\n\n# VTEX IO Release Notes - July 2020\n\nMake room for the VTEX IO Release Notes - July 2020 version, team! \n\nIt is time to step aside from all the world's craziness and restfully read the goodies brought to us in the past month by the VTEX IO team. \n\nStretch your legs, take a deep breath and a sip of coffee: you are about to reach the high-point of your August home-office days with our ***latest news**!\n\nSome of the key changes include:\n\n- 🚀 The new `font-faces.css` file in Store Theme\n- ➕ Product Price blocks for installment options\n- ❌ Animation and Slider blocks deprecation\n- 🐛 Related Products Shelf rendering on mobile devices fix\n\n*And much more*. Cast you eyes on these freshly baked releases right now:\n\n## Features 🚀\n\n- **Cookie Script pixel app** - A VTEX [Cookie Script](https://cookie-script.com/) native integration is now available for your store, making your website cookies comply with GDPR and CCPA. Learn how to install it by accessing the [Cookie Script app documentation](https://developers.vtex.com/docs/vtex-cookie-script). \n\n- **Tawk.to pixel app** - Another pixel app on the front lines: a [Tawk.to](https://www.tawk.to/) native integration is also now available for your store. It allows you to monitor and chat with visitors on either your website, mobile app, or from a free customizable page. Learn how to install it in your VTEX account by accessing the [Tawk.to app documentation](https://developers.vtex.com/docs/vtex-tawk-to).\n\n- **Elfsight pixel app** - They say three is a charm, don't they? A VTEX [Elfsight](https://elfsight.com/?gclid=EAIaIQobChMI4Yejsrnh6gIVVQmRCh0UPgQJEAAYASAAEgIvR_D_BwE) native integration is available, providing widgets to increase sales, engage visitors, collect leads, and more. Learn how to install it in your VTEX account by accessing the [Elfsight app documentation](https://vtex.io/docs/components/pixel/vtex.elfsight/).\n\n- **OneSignal pixel app** - What do we call it? Four is a blast? I think so! A [OneSignal](https://onesignal.com/) native integration is among us, providing web push notifications for customer engagement. Learn how to install it in your VTEX account by accessing the [OneSignal app documentation](https://vtex.io/docs/components/all/vtex.onesignal/).\n\n- **New `font-faces.css` file in the Store Theme app** - Create a CSS global file specifically for your store's fonts and change your store's typography according to your business needs using your Store Theme app code. But keep in mind: the `font-faces.css` file is now mandatory when changing your store's typography using your store theme code, meaning you can no longer upload fonts directly in the app's CSS by overriding files. For more on this topic, access the [Customizing your store's typography](https://vtex.io/docs/recipes/style/customizing-your-stores-typography/) documentation.\n\n## Improvements ➕\n\n- **Product spot price in Google structured data** - The product spot price is now considered in the `lowPrice` field from Google structured data, used to understand and gather information about the content of the store page. This improvement is extremely useful for stores that use Google Shopping, since it will now be able to effectively fetch the product's lowest price (meaning the spot price). \n\n- **Product spot price on search results page** - The product spot price is really deciding to come out. It is now displayed on the store's search results page (whether the store uses VTEX Intelligent Search or the former search solution). \n\n\n*Previously, the product spot price was only available for product detail pages.*\n\n- **Order custom tax data in the `dataLayer` object** - New fields were added to the `dataLayer` object, allowing the store's website to export data related to the order custom taxes. This improvement is extremely useful for stores wishing to handle order custom tax data in Google tracking mechanisms, such as Google Analytics.\n\n- **Product Price blocks for installment options** - The Product Price component now displays all the available installment options according to the desired payment method, thanks to the new blocks `product-installments-list` and `product-installments-list-item`. Previously, the Product Price component only rendered the max number of installments, regardless of the payment method. For more, do not forget to access the [Product Price app documentation](https://vtex.io/docs/components/all/vtex.product-price/).\n\n- **Assets builder's file paths in CSS files** - Media uploaded on Assets builder can now be referenced in your store theme CSS files by adding the accurate file path. Previously, file paths from Assets builder only worked in `blocks.json` and `blocks.jsonc` files. For more on this topic, check out the [Using the Assets Builder](https://vtex.io/docs/recipes/development/using-the-assets-builder/) documentation.\n\n- **List price presentation on product selling price** - The `hasListPrice` prop was added to the `product-selling-price` block from the [Product Price app](https://vtex.io/docs/components/all/vtex.product-price/). It is responsible for defining whether the product should display its [list price](https://help.vtex.com/en/tutorial/prices-v2--tutorials_4393?locale=en) (if any) on its selling price or not. \n\n\n*Product selling price with no list price being displayed.*\n\n\n*Product selling price with the list price also being displayed.* \n\n- **Submenu customization per user navigation [CSS Handles]** - New CSS Handles with modifiers (`submenuWrapper--isOpen` and `submenuWrapper--isClosed`) were added to the [Menu app](https://vtex.io/docs/components/all/vtex.menu/), making it possible to create animation effects when the submenu opens and closes according to the user navigation. For more on how to properly use CSS Handles, access the [Using CSS Handles for store customization](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization) documentation.\n\n\n*Notice how the menu animation showed above only works because the `submenuWrapper--isClosed` Handle is being applied.* \n\n- **Shelf slide dot customization [CSS Handle]** - A new CSS Handle (`dot--isActive`) was added to the [Shelf app](https://vtex.io/docs/components/all/vtex.shelf/), enabling the customization of the shelf active slide dot.\n\n\n*The shelf slide dot highlights the shelf slide currently being hovered on by users.*\n\nWe already are half way through! Hold on tight, some marvelous improvements still await you:\n\n- **Filter Navigator customization on mobile devices [CSS Handles]** - New CSS Handles were added to the [Search Result app](https://vtex.io/docs/components/all/vtex.search-result/) to enable the Filter Navigator component customization on mobile devices. They are, namely: `accordionFilterContainer` , `accordionFilterContent`, `filterBreadcrumbsContent`, and `filterBreadcrumbsText`. \n\n- **Search results page customization per display mode [CSS Handles]** - It became possible to apply CSS classes to search results according to the way they are displayed on the interface! This release marvel is all thanks to the way `galleryItem` CSS Handle (exported by the [Search Result app](https://vtex.io/docs/components/all/vtex.store-components/productspecifications/)) presently behaves when inspected. It now accepts an HTML modifier (`{displayMode}`) meaning that the handle name changes according to the display mode used to render search results. \n\n\n*In the example above, the CSS Handle `galleryItem` presents itself as `galleryItem-inline` when inspected. Notice that the new Handle name is defined according to the display mode set on the search results page.*\n\n- **Product Images' active slide dot customization [CSS Handles]** - A new CSS Handle (`swiperBullet--active`) was added to the [Product Images block](https://vtex.io/docs/components/all/vtex.store-components/productimages)(from the [Store Components app](https://vtex.io/docs/components/all/vtex.store-components/)), enabling the customization of the active slide dot. This handle is extremely useful for scenarios where the Product Images block is used to build a slider component, such as a [Carousel](https://vtex.io/docs/recipes/templates/building-a-carousel-using-slider-layout).\n\n\n*The slider active dot highlights the slide currently being hovered on by users.*\n\n- **Search result's Order By customization [CSS Handles]** - A new CSS Handle (`orderByOptionItem--selected`) was added to the [Search Result app](https://vtex.io/docs/components/all/vtex.search-result/), allowing you to customize the item selected by users on the page's Order by component. \n\n\n\n- **Seller Selector context** - Other VTEX Store Framework apps can now use the context exported by the [Seller Selector app](https://vtex.io/docs/components/all/vtex.seller-selector/) (`SellerContext`) regarding seller data by using the `import { SellerContext } from 'vtex.seller-selector'` expression in the Store Theme code.\n\n - **Breadcrumb structured data** - Previously, neither the [Breadcrumb app](https://vtex.io/docs/components/all/vtex.breadcrumb/) nor the store itself provided the `position` and `itemListElement` data necessary to guide search engines to the current page position in the store category tree. The Breadcrumb app is now configured to have [structured data](https://developers.google.com/search/docs/guides/intro-structured-data), improving your store's SEO.\n\n## Removals ⛔\n\n- **Back button as modal closing button** - The browser's Back button no longer works as a modal closing button when configuring the [Modal Layout app](https://vtex.io/docs/components/all/vtex.modal-layout/). This feature was extremely useful for users from mobile devices since the modal opened in them works as a brand new page. In the meantime, it was leading users to a poor experience when using desktop devices since the Back button wasn't taking users to the previous page as expected. Instead, it only closed modals (if any on the page). In order to improve the website navigation, this feature was removed, meaning that the Modal Layout now depends on its own button in order to be properly closed.\n\n## Deprecations ❌\n\n- **Animation and Slider blocks** - The [Animation](https://github.com/vtex-apps/store-components/blob/master/docs/Animation.md) and the [Slider](https://github.com/vtex-apps/store-components/blob/master/docs/Slider.md) blocks, pertaining to the [Store Components app](https://vtex.io/docs/components/all/vtex.store-components/) were deprecated. Although support for both blocks is still provided, it is strongly recommended to update your store theme with the [Slider Layout](https://vtex.io/docs/components/layout-blocks/vtex.slider-layout/) block in order to keep up with the Slider component evolution. \n\n## Bug fixes 🐛\n\n- **[Product variation sorting on SKU Selector](https://github.com/vtex-apps/store-resources/pull/123)** - Previously, the SKU Selector rendered in a Product Summary Component ([`product-summary-sku-selector` block](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-sku-selector/)) did not respect the Catalog data when displaying product variations. As a result, product variations didn't have a specific sorting when displayed to users, leading to a poor UX. This unexpected behavior is now fixed and the SKU Selector now presents the variations according to how they are ordered in the Catalog module.\n\n- **[`hideImpossibleCombinations` prop behavior](https://github.com/vtex-apps/store-components/pull/828)** - Before this fix, [SKU Selector](https://vtex.io/docs/components/all/vtex.store-components/sku-selector/)'s `hideImpossibleCombinations` prop was not properly hiding impossible specifications (specifications that can't be chosen according to the filter previously selected) when defined as `true` in certain scenarios. In addition, when the prop value was `false`, impossible specifications were not being displayed by the component in an intuitive way. These behaviors are now fixed and the prop is working as expected, improving user experience when using the SKU Selector component. Check out this [link](https://www.loom.com/share/2f11b9f6ae6c4bcf9f23380d3f8bf9eb) to watch a practical demonstration of this bug and its fix.\n\n- **[Slider Layout's slide navigation](https://github.com/vtex-apps/slider-layout/pull/34)** - The [Slider Layout app](https://vtex.io/docs/components/all/vtex.slider-layout/) has gone through fundamental changes in order to improve its usability and therefore the user's experience on it. Previously, the component was showing a mobile delay (mobile users were facing a delay when sliding across products by swiping instead of using the arrow buttons) and a rewind effect (due to the lack of an infinite scroll feature, the component was presenting a rewind effect, taking users back to the *first* displayed product when the *last* one was presented). Both issues were addressed and fixed! Cheers to that! Now the Slider Layout automatically works with a smooth slide transition (infinite scroll effect) and also quickly responds to user interaction on mobile devices.\n\n- **[Related Products Shelf rendering on mobile devices](https://github.com/vtex-apps/shelf/pull/227)** - Due to an implementation detail in the `isMobile` prop, the [Related Products Shelf component](https://vtex.io/docs/components/all/vtex.shelf/) was only being rendered in its desktop mode, even when displayed on mobile devices. This undesirable behavior is now fixed and the Related Products Shelf is working for mobile users as expected.\n\n## Praises ✨\n\nWe would not have been able to deliver so many amazing results during this last month if it were not for the following outstanding contributors:\n\n- [BeatrizMiranda](https://github.com/BeatrizMiranda) *from ACCT*\n- [Matheus Araujo](https://github.com/MatheusR42) *from Corebiz*\n- [Sahan Jayawardana](https://github.com/sahanljc) *from Clouda Inc*\n\nThank you, team! 💪\n\n\n\n```"
}
] |
code_release-notes_95194573
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-43-44/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - Week 43&44/2019\ndescription: \"See what is new in VTEX IO Week 43&44/2019\"\ndate: \"2019-11-13\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-43-44/README.md\"\n---\n\n# VTEX IO Release Notes - Week 43&44/2019\n\nHey team! Another week is dawning!\n\nThe start of the week is always the perfect opportunity to set the pace for the week, month and even life, right? We always promise ourselves to start a new diet, or to better organize our tasks, come up with plans and so on...\n\nFunny how we never seem to the energy to do these things on a **Friday** (we tend to have other priorities :smirk:).\n\nTherefore, bask yourself in this **fresh energy** that only the start of the week can bestow upon us to make it through this week's Release Notes :muscle: You’ll understand why in just a second. It’s just that if there is anything you’ll need an abundant supply of in order to catch up with the latest IO updates, it’s energy to read through everything.\n\nSee for yourself:\n\n### New features :rocket:\n\n- [Hotjar first party app](https://vtex.io/docs/releases/2019-week-43-44/hotjar-first-party-app) - Forget custom HTML tags and rejoice from the services the Hotjar solution provides. A native integration of the solution with IO stores is now a reality thanks to this new 1st party app.\n- [Carousel](https://vtex.io/docs/releases/2019-week-43-44/carousel) - The Carousel component block as we know it makes way for a new Carousel configuration that uses Slider Layout. The more component flexibility, the more customization options available to you!\n\n### Deprecation :x:\n\n- [CSS Selectors](https://vtex.io/docs/releases/2019-week-43-44/css-selectors-deprecation) - The wise Toolbelt has been warning us for the past few days, but you can also read about the deprecation of some Themes CSS selectors here. Check out the details and scenarios that are still allowed.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://vtex.io/docs/releases/2019-week-43-44/platform-performance) - Platform performance improvements are something we always like and want. So give this release a good read to understand what weeks 43 and 44 of 2019 bring in terms of VTEX IO improvement key points.\n- [Store PWA](https://vtex.io/docs/releases/2019-week-43-44/store-pwa) - Once on the Order Placed page, users want to follow their order’s status. A notice prompting the installation of your store’s PWA seems rather strategic at this point, wouldn’t you say? If you agree, then you'll definitely like this improvement.\n- [Menu](https://vtex.io/docs/releases/2019-week-43-44/menu) - If there's something that retailers like, it's code independence. And if there's something we like, it's to see happy retailers! A new configuration of the Menu block allows its content to be edited with Site Editor.\n- [Image](https://vtex.io/docs/releases/2019-week-43-44/image) - Similar to the Menu, uploading Image component content can also be done using the Site Editor. Am I hearing fireworks?\n- [SKU Selector](https://vtex.io/docs/releases/2019-week-43-44/sku-selector) - The SKU Selector is fully loaded this week: it can not only display exclusive images, but also be wholly displayed on the Shelf and even in the Search Results page. Check out the details here!\n\nAre you still with us? I hope so, because there is more to come:\n\n- [Product Specification](https://vtex.io/docs/releases/2019-week-43-44/product-specifications) - You can choose when and on which device to make the Product Specification content collapsible. So much control over a component can seem like fake news, but it's all true thanks to the new component's prop!\n- [Product Summary](https://vtex.io/docs/releases/2019-week-43-44/product-summary) - These past two weeks were not special just for the SKU Selector: the Product Summary didn't just gain a blockClass prop, but also a CSS Handle.\n- [Product Summary Price](https://vtex.io/docs/releases/2019-week-43-44/product-summary-price) - Who doesn't like to know how much they saved when buying a product? The Product Summary Price, knowing that the answer to that question is a resounding \"everyone\", now can display a product's absolute saving to users.\n- [Search Results Page URL](https://vtex.io/docs/releases/2019-week-43-44/search-results-page-url) - The `preventRouteChange` prop expanded and what was valid only for custom pages is now valid for custom-less search result pages too. Apply any filters without worrying about changes to the page's path or structure.\n- [Site Editor](https://vtex.io/docs/releases/2019-week-43-44/site-editor) - GIFs. Yep, that's right. GIFs. G I F S are now properly working in Site Editor.\n\n### Notable bug fixes :bug:\n\n- [Search Results page buttons](https://github.com/vtex-apps/search-result/pull/264) - The `Fetch previous` and `Show more` buttons were vanishing after being clicked on when the previous search results page was either the first or last page with search results. Witchcraft you say? Whatever the case, we've fixed it. In these scenarios, page loading is now rendered before new results are displayed.\n- [Structured data for unavailable products](https://github.com/vtex-apps/structured-data/pull/9) - Unavailable products didn't have their price filled into the page's structured data and were therefore being displayed as free in Google searches. Talk about communication failure :cold_sweat: No unavailable product page structured data will be sent to Google anymore, avoiding erroneous descriptions in the search results and customer confusion.\n- [Two tabs Product Specifications](https://github.com/vtex-apps/store-components/pull/610) - The Product Specification component was facing problems when configured to have two tabs. When expanding the first tab's content (by clicking on a `show more` button) and switching between tabs, users were confronted with a `Show less` button, as if they had already opted to expand that second tab as well. This scenario was corrected and the tabs now act independently :muscle:\n\n```"
}
] |
code_release-notes_87ad9f2e
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-45-46/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - Week 45&46/2019\ndescription: \"See what is new in VTEX IO Week 45&46/2019\"\ndate: \"2019-11-26\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-45-46/README.md\"\n---\n\n# VTEX IO Release Notes - Week 45&46/2019\n\nHey, team! Welcome to the **Black** VTEX IO Release Notes.\n\nYep, that's right. If this Friday is **Black Friday**, you can call us **Black Release Notes** this week because we are thrilled with this long awaited event being just around the corner.\n\nWhether retailer or end user, I do hope that your checklist for this black week is ready, because mine is :heavy_check_mark: And guess what else? It envolves reading the entire Release Notes.\n\n### New features :rocket:\n\n- [Site Editor](https://vtex.io/docs/releases/2019-week-45-46/site-editor) - They say 1 is few, 2 is good and 3 is a party. If a release for the Site Editor is already incredible, picture 3? Check out the new Topbar, complete with tooltips and new modal texts for the admin section.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://vtex.io/docs/releases/2019-week-45-46/platform-performance) - We always rejoice from performance improvements, and I promise you that this one involving data fetching is legit. Check out the VTEX IO performance improvement for week 45 and 46 of 2019.\n- [Product Specifications](https://vtex.io/docs/releases/2019-week-45-46/product-specifications) - The Product Specifications `visibleSpecifications` and `hiddenSpecifications` props can now be edited using the admin's Site Editor. This Site Editor never tires of being a hero for code-less people, for real...\n- [Breadcrumb](https://vtex.io/docs/releases/2019-week-45-46/breadcrumb) - If you've had a good week, Breadcrumb had a better one! The component gained two new props (`homeIconSize` and `caretIconSize`), new Handles (`homeLink` and `termArrow`) and other improvements.\n- [CSS Handles](https://vtex.io/docs/releases/2019-week-45-46/css-handles) - The Breadcrumb was not the only one to have been gifted Handles this week. `savingPriceValue` and `savingPriceLabel` also had a lucky week and gained their own CSS Handles.\n- [Search query](https://vtex.io/docs/releases/2019-week-45-46/search-query) - Shall we celebrate search query's independence from the facets query? Even when the latter doesn't return any results, the former renders data fetched by the `productSearch` query, providing users with search results regardless.\n- [Search Result Gallery](https://vtex.io/docs/releases/2019-week-45-46/search-result-gallery) - During the Black Friday week, the e-commerce gods have bestowed the blessing upon the Gallery component, making it responsive and willing to accept different values for (almost) any existing device.\n- [Search Result OrderBy](search-result-orderby) - OrderBy’s new `hiddenOptions` prop does away with the component’s forced exhibitionism. Its options can now either be hidden or displayed according to the retailer’s chosen scenario.\n\n### Notable bug fixes :bug:\n\n- [Filter Navigator](https://github.com/vtex-apps/search-result/pull/272) - The release of the `preventRouteChange` prop in search result pages was [announced](link Release) during the last Release Notes and, believe it or not, was already cause for uncertainty. When a category was selected and then removed from the Filter Navigator, the URL was keeping the former category, showing inaccurate data to the user. This bug was already fixed and the prop is alive and well. Booyah!\n- [Highlight resize](https://github.com/vtex-apps/admin-pages/pull/303) - When editing a block with the admin's Site Editor, its height may change according to its new configurations, right? The problem was that the `HighlightOverlay`, responsible for highlighting the block was being edited on the Site Editor's interface, was shy and kept the original height, thereby impairing the display of the new configurations. It's now learned to be more receptive to change and adapts according to the block's new height.\n\n```"
}
] |
code_release-notes_d62feb8d
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-32-33/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 32&33/2019\ndescription: \"See what is new in VTEX IO Week 32&33/2019\"\ndate: \"2019-08-22\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-32-33/README.md\"\n---\n\n# VTEX IO Highlights - Week 32&33/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nSince we were slightly behind schedule with the release, this week’s release notes come in a **double feature format** to put us back on track again!\n\nWithout further ado, here’s a sneak peek at key changes made in the last couple of weeks:\n\n> :bell: Keep up-to-date with VTEX IO release notes! Simply click on **Releases only** in this page’s upper right corner **Watch** box.\n\n### New features :rocket:\n\n- [Internal URLs link in banners](internal-urls-link-in-banners.md) - Easily link internal URLs to a banner with the help of CMS’s new Storefront field.\n- [accessiBe first party app](accessibe-first-party-app.md) - Get your hands on a first-party integration with the accessiBe solution.\n- [Extension points on Order Placed page](extension-points-on-the-order-placed-page.md) - Customize a store’s Order Placed page using extension points.\n\n### Deprecations :x:\n\n- [Pages Settings tab](pages-settings-tab.md) - The Pages Settings tab no is longer available in the CMS section.\n\n### Improvements :heavy_plus_sign:\n\n- [Performance da plataforma](platform-performance.md) - Understand what the VTEX IO performance improvement key points were.\n- [Drawer component](drawer-component.md) - Customize your store Drawer’s behavior and appearance using the component’s 3 new props and CSS handles.\n- [Breadcrumb on mobile mode](breadcrumb-on-mobile-mode.md) - Make the Breadcrumb component available for mobile users.\n- [Image thumbnails](image-thumbnails.md) - Choose whether a product’s thumbnail images will be displayed vertically or horizontally.\n- [Custom pages URL changes](custom-pages-url.md) - New browser filter prop which allows custom pages to keep the URLs unchanged even when filters are applied.\n- [Search Result](search-result.md) - Display how many items the user is seeing and how many items are left on the search results page.\n- [Minicart component](minicart-component.md) - The new Minicart component prop enables redirecting users to any page the retailer chooses when clicking the “Finish Shopping” button.\n\n### Notable bug fixes :bug:\n\n- [Subscription on unavailable products](https://github.com/vtex-apps/store-components/pull/545) - Adding email notifications for when unavailable products are again available no longer gives users an error.\n- [Telemarketing Login](https://github.com/vtex-apps/telemarketing/pull/52) - Before this fix, when logging in to a store which had a telemarketing profile, users would encounter problems in rendering the Menu component, which would have stayed behind the Search Bar.\n- [Buy-button redirect](https://github.com/vtex-apps/store-discussion/issues/64) - The Buy Button no longer redirects users to an empty cart when the request to add a product to the cart take too long. ℹ️This behavior only was enabled when `isOneClickBuy` was set to `true`.\n- _Timeout errors in canonical routes_ - To avoid timeout errors, the canonical routes response wait time was increased. :information_source: This bug fix Pull Request was performed is a private VTEX repository.\n- [Storefront carousel schema](https://github.com/vtex-apps/carousel/pull/82) - Carousel schema was reordered in the Admin’s Storefront section in order for image uploads to be displayed first.\n- [Icon button inside forms](https://github.com/vtex/styleguide/pull/742) - With this bug fix, you can use an icon button inside a `<form>` without it automatically becoming a submit, saving the form when clicked.\n- [Duplicated Minicart items](https://github.com/vtex-apps/minicart/pull/174) - When the same item is repeatedly added by a user to the Minicart, the component will henceforth take the added quantity into account without displaying any bugs.\n- [External URLs assignment](https://github.com/vtex-apps/store-discussion/issues/81) - When specified in a `menu-item block` , external URLs no longer lose their query string.\n\n```"
}
] |
code_release-notes_9eac6b7e
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-26/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 26/2019\ndescription: \"See what is new in VTEX IO Week 26/2019\"\ndate: \"2019-07-03\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-26/README.md\"\n---\n\n# VTEX IO Highlights - Week 26/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nHere's a sneak peek at the key changes made in the last week:\n\n> 🔔 Keep up with VTEX IO release notes! Just click on <strong>Releases only</strong> in the <strong>Watch</strong> box on the right upper corner of this page.\n\n### New features 🚀\n\n- [Brand component](brand-component.md) - Show a product's brand name or logo in your Product Details page with this new component.\n\n### Improvements ➕\n\n- [Toolbelt dependency on Housekeeper](toolbelt-dependency-on-housekeeper.md) - Housekeep API is presently used by VTEX IO Toolbelt, giving app updates more reliability in a workspace.\n- [Search Bar component](search-bar-component.md) - Increase the search results preview performance with this new Search Bar component improvement.\n- [React builder optimization](react-builder-optimization.md) - The webpack logic has now been improved with the React builder optimization, leading to an impressive reduction in resources.\n- [Product Description component](product-description-component.md) - It is now possible to display a product description in your store regardless of its size.\n\n### Notable Bug Fixes 🐛\n\n- [Login infinite loop](https://github.com/vtex-apps/login/pull/135) - Users without a set session cookie will no longer encounter problems with infinite loop logins on any store website.\n\n```"
}
] |
code_release-notes_0763fe55
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-28/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 28/2019\ndescription: \"See what is new in VTEX IO Week 28/2019\"\ndate: \"2019-07-17\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-28/README.md\"\n---\n\n# VTEX IO Highlights - Week 28/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nHere’s a sneak peek at the key changes made in the last week:\n\n> :bell: Keep up with VTEX IO release notes! Just click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- [Sidecar pixel app](sidecar-pixel-app.md) - Get your hands on a first-party integrations with the Sidecar solution.\n- [Native A/B Testing](native-ab-testing.md) – Increase your store’s conversion rate by performing native VTEX IO A/B testing, now available to clients platform-wide.\n- [Typography customization](typography-customization.md) - Easily customize your store’s typography through Storefront.\n\n### Improvements :heavy_plus_sign:\n\n- [Submenu behaviour](submenu-behavior.md) - The Menu component now has a better behavior when it is triggered to expand.\n- [React render performance](react-render-performance.md) - VTEX IO now implements the new React feature that allows component data reuse using hooks.\n\n### Notable bug fixes :bug:\n\n- [RichText content](https://github.com/vtex-apps/admin-pages/pull/241) - RichText fields edited through storefront no longer display a hash id.\n- [Block title](https://github.com/vtex-apps/render-runtime/pull/345) - The block `title` prop was used to edit the block name displayed in the Storefront section, in the new CMS version. This Pull Request aims to fix it since it was broken during the latest releases.\n- **“Socket Hang Up” errors** - Recurring problems with server-side rendering, asset fetching and graphql queries were solved, ensuring that the end user no longer faces page loading errors. :information_source: This bug fix pull Request was done is a VTEX private repository.\n\n```"
}
] |
code_release-notes_9a31e785
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-29/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 29/2019\ndescription: \"See what is new in VTEX IO Week 29/2019\"\ndate: \"2019-07-25\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-29/README.md\"\n---\n\n# VTEX IO Highlights - Week 29/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nHere's a sneak peek at key changes made in the last week:\n\n> :bell: Keep up with VTEX IO release notes! Simply click on **Releases only** in the **Watch** box in the upper right corner of this page.\n\n### New features :rocket:\n\n- [Store Theme blocks structure](store-theme-blocks-structure.md) - Gain more flexibility when organizing your store theme blocks as wanted.\n- [Price internationalization](price-internationalization.md) – Overcome internationalization hurdles by changing the behavior of the currency in which prices are being displayed in your store.\n- [Server Timing](server-timing.md) – Monitor the performance of each sent request with the Server timing feature.\n\n### Improvements :heavy_plus_sign:\n\n- [PowerReviews pixel app](powerreviews-pixel-app.md) - It now has a first-party integration with PowerReviews Checkout Beacon solution.\n- [Minicart component](minicart-component.md) - New properties enable the displaying of the total item and value quantity in the component.\n\n### Notable bug fixes :bug:\n\n- [Cookies transfer to `graphql-server`](https://github.com/vtex-apps/admin-graphql-ide/pull/5) - Cookies that were lost when going through the app [Admin GraphQL IDE](https://github.com/vtex-apps/admin-graphql-ide) were recovered and are now being correctly redirected to the `graphql-server`.\n- [Non editable blocks showing up](https://github.com/vtex-apps/admin-pages/pull/245)) - Non editable blocks no longer show up in Storefront’s editing section in CMS.\n\n```"
}
] |
code_release-notes_17bc63ef
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-27/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 27/2019\ndescription: \"See what is new in VTEX IO Week 27/2019\"\ndate: \"2019-07-10\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-27/README.md\"\n---\n\n# VTEX IO Highlights - Week 27/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nHere's a sneak peek at the key changes made in the last week:\n\n> 🔔 Keep up with VTEX IO release notes! Just click on <strong>Releases only</strong> in the <strong>Watch</strong> box on the right upper corner of this page.\n\n### New features 🚀\n\n- [Storefront page customization by URL](storefront-page-customization-by-url.md) - Customize your store through Storefront faster by simply navigating to the desired page using its URL.\n- [Product Identifier component](product-identifier-component.md) - Display products/SKU IDs and reference anywhere on your Product page, Shelf and Search Results.\n- [Search Bar component behavior](search-bar-component-behavior.md) - Use its new prop as `true` and enable store users to search by the desired category, brand and collection.\n\n### Improvements :heavy_plus_sign:\n\n- [Warning disclaimer when in master](warning-disclaimer-when-in-master.md) - Storefront now send a warning when editing a store in a master workspace.\n- [Search query](search-query.md) - The Search component now takes 50% less time to display results to users.\n- [Shelf rendering](shelf-rendering.md) - The Shelf component now has a faster user loading time.\n\n### Notable bug fixes :bug:\n\n- [Auto scroll](https://github.com/vtex-apps/admin-pages/pull/233) - With this fix, users will no longer have a negative experience when trying to select a block to customize in Storefront in the new CMS.\n- [Blocks without schema](https://github.com/vtex-apps/admin-pages/pull/230) – When editing a store using Storefront, users can now click on blocks that don’t have schema, such as rows and columns, without getting back an error.\n- [SKU Selector](https://github.com/vtex-apps/store-components/pull/517) - The SKU Selector no longer vanishes for the user when there is just one specification to be chosen.\n- [Shelf image](https://github.com/vtex-apps/shelf/pull/156) - Issues with Shelf Component image size shifting are fixed. This bug fix removes the image flickering that were negatively impacting mobile browsing.\n\n```"
}
] |
code_release-notes_6614aff7
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-05/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - May 2020\ndescription: \"See what is new in VTEX IO for May 2020\"\ndate: \"2020-06-18\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-05/README.md\"\n---\n\n# VTEX IO Release Notes - May 2020\n\nWelcome to the May 2020 VTEX IO Release Notes, team! \n\nThe VTEX IO Release Notes is marking it's **first anniversary** online and we've decided to celebrate this first year by doing what we do best: introducing our users to eagerly awaited configs. \n\nSome of the key highlights are:\n\n- :heavy_plus_sign: Layout conditioned by product specifications;\n- :x: Product Summary Price and Product Price blocks deprecation;\n- :bug: Links working in Brand component.\n\nShall we then start reading this Release Notes gem for May? \n\n## Improvements :heavy_plus_sign:\n\n- **Product prices with tax** - Blocks exported by the [Product Price](https://vtex.io/docs/components/all/vtex.product-price) app are now able to render their text messages and price variables with tax values considered. \n\n- **Infocard's new** `callToActionLinkTarget` **prop** - The `callToActionLinkTarget` prop from the [Infocard](https://vtex.io/docs/components/all/vtex.store-components/infocard/) block is now available for the Edition in the admin's Site Editor. \n\n- **CSS Handles** - New CSS Handles always herald good news. Let's rejoice: `firstVisible` and `lastVisible` have arrived to the [Slider Layout app](https://vtex.io/docs/components/all/vtex.slider-layout), allowing you to customize the first and the last visible item on a slide. In addition, the [Rich Text](https://vtex.io/docs/components/all/vtex.rich-text/) and the [Search Results](https://vtex.io/docs/components/all/vtex.search-result/) also gained new Handles: namely the `wrapper` and the `accordionFilterOpen` for mobile devices.\n\n- **Product Specifications block and Search Results filters customization** - It is now possible to independently customize each of the UI product specifications and the search filters. All this thanks to adding modifiers and new attributes linked to HTML elements. For more info, access the [Search Results app](https://vtex.io/docs/components/all/vtex.search-result/) and [Product Specifications block](https://vtex.io/docs/components/all/vtex.store-components/productspecifications/) documentation, in addition to going through the recipe on [Using CSS Handles for store customization](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization).\n\n- **Add to Cart button message** - Define which message will be displayed on the [Add to Cart Button](https://vtex.io/docs/components/all/vtex.add-to-cart-button) thanks to the block's new `text` prop. In addition, you can define a text message that will be rendered when the product is not available for purchase - thanks to another new prop called `unavailableText`. \n\n- **Newsletter in Site Editor** - The [Newsletter](https://vtex.io/docs/components/all/vtex.store-components/newsletter/) is finally in Site Editor! The component can now be edited using your account's admin.\n\n- **Layout conditioned by product specifications** - The [Condition Layout](https://vtex.io/docs/components/all/vtex.condition-layout) now works with product specifications, thanks to the new value `specificationProperties` for the `subject` prop. That's right: you can now define which product specifications should trigger the rendering of predefined content! Cheers to that! \n\n- **CSS subfolders** - The folder where your theme's app CSS files are stored (called `css` and allocated in the main `styles` folder) now supports subfolder organization, which means that you can organize your CSS files as you wish from now on! \n\n- **Empty Minicart state** - This one should be a good surprise to users: The Minicart empty state was improved. What was merely a rich text gave way to more user friendly UI, having an empty cart icon. \n\n- `remove-button`**'s new props** - The [Product List](https://vtex.io/docs/components/content-blocks/vtex.product-list/) app's `remove-button` block received two new strategically important props: `displayMode` and `variation`. The first defines whether the block should be displayed as an icon or as a text (allowing you to [create confirmation modals when displayed as an icon](https://vtex.io/docs/recipes/templates/creating-modals-using-icons/)). In turn, the second prop defines the remove button visual prominence when it is displayed as a text based on the [VTEX Styleguide](https://styleguide.vtex.com/#/Components/Forms/Button). \n\n## Deprecations :x:\n\n- **Product Summary Price and Product Price blocks** - The Product Summary Price and the Product Price blocks, respectively, pertaining to the [Product Summary](https://vtex.io/docs/components/all/vtex.product-summary) and the [Store components](https://vtex.io/docs/components/all/vtex.store-components) apps, were deprecated in favor of the [**Product Price**](https://vtex.io/docs/components/all/vtex.product-price/) app. Although support for these blocks is still granted, it is strongly recommended to update your store theme with the Product Price's blocks in order to keep up with the component's evolution.\n\n## Bug fixes :bug:\n\n- **Minicart item list** - When more than 1 SKU with attachments was added to the [Minicart](https://vtex.io/docs/components/all/vtex.minicart) (version 1 and 2), the component interpreted that only 1 should receive the chosen attachment, while the other SKUs would not receive it. This bug was now fixed in both versions and the Minicart lists the correct SKU number with their respective attachment. \n\n- [**Slider Layout dots on mobile**](https://github.com/vtex-apps/slider-layout/pull/21) - The pagination dots, located below the component built using [Slider Layout](https://vtex.io/docs/components/layout-blocks/vtex.slider-layout), were not rendering slides when clicked on using a mobile device - contrary to the Slider's arrows. The pagination dots are now working as expected and users can click on them to change slides.\n\n- [**Image link editing in Site Editor**](https://github.com/vtex-apps/store-image/pull/15) - \nWhen an image link was added to the Image component ([Store Image](https://vtex.io/docs/components/all/vtex.store-image/) app) using the admin's Site Editor, an unexpected error took place: the `newTab` toggle button was not working properly. This was now fixed and users can correctly configure image links to open in new tabs when editing the Image component in Site Editor.\n\n- [**Links in Brand component**](https://github.com/vtex-apps/store-components/pull/774) - The Store Component's [Product Brand block](https://vtex.io/docs/components/all/vtex.store-components/productbrand/) allowed the creation of links in the brand product icon, by using the `logoWithLink` prop. The prop was not functioning properly, which led to this functionality being forgotten. Thanks to a fix, the prop is now 100% available and ready for use!\n\n## Praises :sparkles:\n\n- [pgrimaud](https://github.com/pgrimaud) *from Big Youth*\n- [LucasCastroAcctGlobal](https://github.com/LucasCastroAcctGlobal) *from ACCT*\n- [BeatrizMiranda](https://github.com/BeatrizMiranda) *from ACCT*\n\n\n```"
}
] |
code_release-notes_5f8fab17
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-02/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - February 2020\ndescription: \"See what is new in VTEX IO February 2020\"\ndate: \"2020-03-16\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-02/README.md\"\n---\n\n# VTEX IO Release Notes - February 2020\n\nI don't know if it was the extra day we had due to the leap year or the Carnival rest (or should I say *party*? :grimacing:), but something is certain: our wonderful development team was truly inspired in February! \n\nBrace yourselves... This month's VTEX IO Release Notes is here and you'll need to muster all the energy you can to catch up with everything that has been prepared for you. I really do mean it! Just check it out:\n\n## Special announcements :speaker:\n\n- **Exception for the CSS Selectors deprecation**: Previously, no blocks could be customized by CSS Selectors, remember? This breaking change and the reasons that led to it were announced in the [Release Notes for weeks 43 and 44 of 2019](https://vtex.io/docs/releases/2019-week-43-44/css-selectors-deprecation). Now, this scenario has undergone further changes. Apps that are not yet flexible will be able to CSS Selectors as an exception. They are: `vtex.my-account@1.x`, `vtex.my-orders@3.x` and `vtex.login@2.x`,\n\n- **Changes to the VTEX IO Closed Beta list workflow** - VTEX IO now has a new workflow to require platform development permissions! [Find out more details](https://vtex.io/docs/releases/2020-02/vtex-io-closed-beta-list) about the change and what you will need to do from now on.\n\n## Features 🚀\n\n- **VTEX init** - The creation of new storefronts using the VTEX IO Store Framework will limit itself to the `store` option when running the `vtex init` command. `store` is a basic boilerplate, unlike the previous Store Theme that already had a lot of preset configurations and customization. Good news for Store Framework beginners!\n\n- **Assets Builder** - A brand new Builder to handle assets that are used in your theme's blocks. Magical! Check out the recipe on [how to configure and use it](https://vtex.io/docs/recipes/development/using-the-assets-builder). \n\n- **Modal Layout** - The Modal Layout is out and ready for use. Find out how to create modals for your store in its [documentation](https://vtex.io/docs/components/layout-blocks/vtex.modal-layout/).\n\n- **Sticky Layout** - Endless praise to our dev team that deliver not just one, but two new Layouts releases. You are now able to fix elements in place on the interface, thereby making blocks follow user navigation when scrolling thanks to the [Sticky Layout](https://vtex.io/docs/components/layout-blocks/vtex.sticky-layout/)! \n\n- **Shelf** - Have you heard the latest? Shelf block is now configured with [Slider Layout](https://vtex.io/docs/apps/layout-blocks/vtex.slider-layout). When listing context, you'll be able to display the desired products in an easier and more practical way. Find out how by reading the [documentation](https://vtex.io/docs/components/content-blocks/vtex.shelf/)!\n\nStill with us? It gets better...\n\n- **Components Debugger** - If you thought you had problems decrypting each component's Handles, the dog days are now over because the Components Debugger has landed. Check out the recipe on [using CSS Handles for store customization](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization) and begin using the Components Debugger now. \n\n- **Toolbelt** - A notification is now triggered in your terminal when the `vtex link` command is not running anymore, meaning when your link has died. Can I get an amen? But remember: this new feature is only valid for MAC and Linux at the moment. \n\n- **Alexa Certify Code** - Natively integrate with Amazon's [Alexa solution](https://vtex.io/docs/components/all/vtex.alexa-certify-code/) now! \n\n- **Braspag Cybersource Fingerprint** - Make way for there is yet another pixel bringing native integration. It is the [Braspag's Cybersource anti-fraud](https://vtex.io/docs/components/all/vtex.cybersource-fingerprint/)!\n\n- **UserData Event** - It's up and running, yes! [Set up the Google Tag Manager UserData Event](https://vtex.io/docs/recipes/store-management/setting-up-google-tag-manager) in your store and verify data related to your store logged in users using the Google Analytics.\n\n## Improvements ➕\n\n- **SEO** - Bad SEO practices? Not here. New URLs that are generated based on a change in a product/category/brand name are no longer indexed by Google even if the content is invalid. Instead, a redirect is created from the old URL to the new one.\n\n- **Order Placed** - Previously, [Order Placed](https://vtex.io/docs/components/content-blocks/vtex.order-placed/readme) was a big monolithic block. Now, Order Placed v2 is launched. Broken into small and customizable blocks, it allows you to customize the order placed page as you wish! Yay! \n\n- **React app dependencies** - The wise Toolbelt will now automatically update an App React's dependencies located in the app's `package.json` file to keep them in line with Render's dependencies list. Find out more details on this improvement [here](https://vtex.io/docs/releases/2020-02/react-app-dependencies)!\n\n - **SVG's size** - The `viewbox` prop for [Store Icons](https://vtex.io/docs/components/all/vtex.store-icons/) now accepts other values aside from 16x16px for the following block icons: `search-bar`, `login` and `minicart`. \n\n- **Header layout** - Making a header layout change when scrolling it sounds unrealistic to you? Let me break it to you... it's not! Open the [Header documentation](https://vtex.io/docs/components/content-blocks/vtex.store-header/) to see for yourself. \n\n- **Login interface** - New prop for the following area: `logInButtonBehavior`. It sets the Login block interface either to `popover` or `link` . Find out more about its implementation by accessing the [Login documentation](https://vtex.io/docs/components/all/vtex.login/). \n\nBreathe in and relax, because we still have more... \n\n- **CSS Handles** - Our constantly acclaimed CSS Handles release is also present this month with new CSS Handles for the [Search Result](https://vtex.io/docs/components/content-blocks/vtex.search-result/) page.\n\n- **Shelf IDs** - The [Shelf](https://vtex.io/docs/components/content-blocks/vtex.shelf/) `trackingId` prop now enables you to identify, using a Shelf ID, which Shelf actually had its content accessed and triggered the Google Analytics event. \n\n- **Product Images** - Deciding where to position product video on Product Images thumbnails is not an impossible task anymore thanks to the [Product Image](https://vtex.io/docs/components/content-blocks/vtex.store-components/product-images)'s new `contentOrder` prop. \n\n- **Search Bar** - Previously, you couldn't keep the search icon after entering a text in the search bar. Boring... this scenario changed once the `DisplayMode` prop arrived. Check out the [documentation](https://vtex.io/docs/components/content-blocks/vtex.store-components/search-bar)! \n\n## Notable bug fixes 🐛\n\n- **[Minicart on hover](https://github.com/vtex-apps/minicart/pull/208)** - Several issues were solved with this one: 1) hovering now only works on desktop mode; 2) When hovered, the Minicart remains open for as long as the user is interacting with it; 3) If the Minicart icon is clicked on, it will behave normally and will be closed when the user clicks outside its area. The Minicart previously had run into some trouble and none of the above were functioning properly...\n\n- **[Measures for product images](https://github.com/vtex-apps/store-theme/pull/197)** - The [Product Summary Image](https://vtex.io/docs/components/content-blocks/vtex.product-summary/product-summary-image) now ensures that the images displayed take up the same space on the interface, having identical measures, regardless of their original size in the Catalog thanks to the new props `height` and `width`. \n\n- **[Locale Switcher](https://github.com/vtex-apps/locale-switcher/pull/17)** - Long time no see, Locale Switcher... Previously, the block would disappear when the binding default language was used during navigation. Everything was now solved and the block is always present on the interface.\n\n- **Product Impression event** - The Product Impression Event failed to be triggered in two different scenarios: in incomplete [Search Results product aisles]((https://github.com/vtex-apps/search-result/pull/307)) and on the [Related Products Shelf](https://github.com/vtex-apps/shelf/pull/211). everything is working as intended now (and everything triggered as it should be). \n\n- **[SKU Selector](https://github.com/vtex-apps/product-summary/pull/237)** - Users were being redirected to the SKU page without choosing at least a product specification when on the Shelf or Search Results pages. The new `initialState` prop now comes with the `empty` default value and thus users will only be redirected after choosing specification for the SKU in question.\n\n- **[Product Summary Image](https://github.com/vtex-apps/product-summary/pull/236)** - The `mainImageLabel`, which defines which product image should be present on the Product Summary, didn't change even when users interacted with the SKU Selector. This confused users, since the image didn't necessarily portray the product specifications chosen by the user. This has now changed: the `mainImageLabel` only appears in the product summary when no specification has been selected, meaning that the `initialState` is `empty` (default behavior, thanks to the bug fix above hehe).\n\n\n```"
}
] |
code_release-notes_48389b66
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-30/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 30/2019\ndescription: \"See what is new in VTEX IO Week 30/2019\"\ndate: \"2019-08-02\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-30/README.md\"\n---\n\n# VTEX IO Highlights - Week 30/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nHere's a sneak peek at key changes made in the last week:\n\n> :bell: Keep up-to-date with VTEX IO release notes! Simply click on **Releases only** in the **Watch** box in the upper right corner of this page.\n\n### Improvements :heavy_plus_sign:\n\n- [Navigation arrows on thumbnails](arrows-pdp-thumbnails.md) - Add navigation arrows to your PDP images.\n- [Link brand component](brand-component-link.md) - Our brand component may take the user to the brand's page.\n- [Full category tree on events](category-tree-events.md) - Track your product's full category-tree on Google Analytics.\n- [Menu-item component with icon](icon-menu-item.md) - Add an icon next to each menu-item text and create custom menus.\n- [Image with link](image-component-link.md) - Our image component now supports the prop link.\n- [New sorting criteria](new-orderby-options.md) - Use these new criteria to sort your products.\n- [Shelf hiding unavailable items](shelf-hide-unavailble.md) - Prevent out-of-stock products from appearing on your shelf.\n\n### Notable bug fixes :bug:\n\n- [Carousel autoplay](https://github.com/vtex-apps/carousel/pull/81) - Our carousel autoplay functions properly again.\n- [Price range](https://github.com/vtex-apps/search-result/pull/213) - Price range filter now functions properly both on desktop and mobile mode\n\n```"
}
] |
code_release-notes_2bf3daa3
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-37/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 37/2019\ndescription: \"See what is new in VTEX IO Week 37/2019\"\ndate: \"2019-09-23\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/README.md\"\n---\n\n# VTEX IO Highlights - Week 37/2019\n\nHey! 👋 Welcome to VTEX IO Release Notes for week 37 of 2019!\n\nYou might have noticed that last week’s Release Notes didn’t reach you. Not to worry. To put you on track with VTEX IO, this week will have **two** publications! 🎉\n\nThrilled to announce that this week's first Release Notes brings several long awaited releases and innovative such as **SEO strategy** improvement and the **new Search GraphQL app**.\n\nDon't get left behind with the latest on these and other key changes. Get a sneak peek at this week's main releases:\n\n> :bell: Keep up with VTEX IO release notes! Just click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- [Hot Reload](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/hot-reload.md) - The time when you had to hit the refresh button to be able to see your code changes is long gone thanks to our Hot Reload.\n- [Bazaarvoice first party app](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/bazaarvoice-first-party-app.md) - Get your hands on a first-party integration with the Bazaarvoice solution.\n- [Flexible Search Results Page](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/flexible-search-results-page.md) - Search Results Pages customization just became more powerful with `flex-layout`.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/platform-performance.md) - Understand what were the VTEX IO performance improvement key points for week 37 of 2019.\n- [SEO strategies](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/seo-strategies.md) - If there is anything as sought after as a stable platform, it's SEO improvement. Therefore, check out our latest SEO releases for your VTEX IO store.\n- [Search GraphQL](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-37/search-graphql.md) - The `store-graphql` morphed into `search-graphql`, which took over responsibility for your store's GraphQL search related queries.\n\n### Notable bug fixes :bug:\n\n- [Site Editor blocks code](https://github.com/vtex-apps/admin-pages/pull/275) - Whenever a block is selected in Site Editor, the server responds with the latest code, allowing blocks to be edited with the most up-to-date content.\n- [Site Editor `HiglightOverlay` component](https://github.com/vtex-apps/admin-pages/pull/278) - Previously, when clicking on a block that did not exist in your store, the Site Editor's section iframe would not work due to an unexpected behavior of the HighlightOverlay component (responsible for displaying on the screen which component from the list the user is currently editing). This behavior was remedied.\n- [Child block customization on Site Editor](https://github.com/vtex-apps/admin-pages/pull/269) - Site Editor encountered rendering problems when users tried to edit a child block listed in a parent block. This fix enables the customization of blocks which are listed in another Site Editor block list to occur normally.\n\n```"
}
] |
code_release-notes_36f208af
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-36/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 36/2019\ndescription: \"See what is new in VTEX IO Week 36/2019\"\ndate: \"2019-09-13\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/README.md\"\n---\n\n# VTEX IO Highlights - Week 36/2019\n\nWelcome to yet another VTEX IO weekly release notes, this one being more than special because we are announcing the release of our brand new VTEX IO documentation website.\n\nHonestly, why are still reading the into after such news? Scroll down and have a look at last week's key changes:\n\n> :bell: Keep up with VTEX IO release notes! Just click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- [VTEX IO docs](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/vtex-io-docs.md) - You didn't misread! The dim light at the end of the tunnel just got brighter: the new VTEX IO documentation website is up and ready for you to access.\n- [Minicart Sandbox blocks](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/minicart-sandbox-blocks.md) - Customize your Minicart footer using Sandbox blocks.\n- [Google Analytics `productView` event](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/google-analytics-productview-event.md) - Get more insight into your store's user behavior by tracking their navigation between SKUs.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/platform-performance.md) - Understand last week's VTEX IO performance improvement key points.\n- _Storefront name change_ - Your account Admin's Storefront section, responsible for defining your store's front-end content is now called **Site Editor**. Commit to memory!\n- [Events context](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/events-context.md) - Create a web app with more ease with help from Events' expanding functionalities.\n- [Google Analytics `orderPlaced` event ](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-36/google-analytics-orderplaced-event.md) - Make your Google Analytics metrics more reliable with the `orderPlaced` event trigger improvement.\n\n### Notable bug fixes :bug:\n\n- [Site Editor's component list](https://github.com/vtex-apps/admin-pages/pull/268) - Previously, site-wide components were not displayed in Site Editor's component list. With this bug fix, the full list will be displayed to the user.\n- [Pickup point ID](https://github.com/vtex-apps/store-components/pull/577) - The Pickup point ID should not have been displayed in the Shipping Simulator as was the case. This bug fix remedies this scenario.\n- [Google Tag Manager app events](https://github.com/vtex-apps/google-tag-manager/pull/25) - Events sent by the Google Tag Manager app were inconsistent with regards to the sent ID, which sometimes pertained to the SKU while other times to the product. This fix ensures that all events are now sent using SKU IDs.\n\n```"
}
] |
code_release-notes_5ccce2ce
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-31/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 31/2019\ndescription: \"See what is new in VTEX IO Week 31/2019\"\ndate: \"2019-08-15\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-31/README.md\"\n---\n\n# VTEX IO Highlights - Week 31/2019\n\nWelcome to the VTEX IO weekly release notes!\n\nHere’s a sneak peek at key changes made in the week before last:\n\n> :bell: Keep up-to-date with VTEX IO release notes! Simply click on **Releases only** in the **Watch** box in the upper right corner of this page.\n\n### New features :rocket:\n\n- [Color name on SKU Selector](color-name-sku-selector.md) - Display the selected SKU’s color name.\n- [Change image on hover](change-image-on-hover.md) - Show a secondary product image by hovering it.\n- [Storefront language selector](storefront-language-selector.md) - Storefront now has a language selector.\n\n### Improvements :heavy_plus_sign:\n\n- [Minimum items on shelf](minimum-items-shelf.md) - Control how many items can be displayed on the smallest screen size.\n- [Search Result layout on mobile mode](hide-layout-switcher-mobile.md) – Switch the mobile Search Result layout with the new mobileLayout prop.\n- [Page title of contextless routes](custom-title-standard-page.md) - Set a custom title on a standard page.\n\n### Notable bug fixes :bug:\n\n- [Tablet responsiveness](https://github.com/vtex-apps/store-discussion/issues/56) - The responsiveness of our framework on tablets and mobile in landscape mode has improved.\n- [Minicart not updating](https://github.com/vtex-apps/minicart/pull/171) - Minicart now updates modified items directly at checkout.\n- [PageView event](https://github.com/vtex-apps/store/pull/312) - The pageView event is now properly sent along with the pageTitle prop.\n- [Sorting dropdown](https://github.com/vtex-apps/search-result/pull/217) - Our dropdown sorting menu now adapts its size dynamically, not breaking the line.\n- [Search bar preview](https://github.com/vtex-apps/store-components/pull/539) - The search bar preview adapts its size alongside the search bar size.\n- [Dots without CSS](https://github.com/vtex-apps/carousel/pull/83) - The CSS is now being applied on carousel dots.\n\n```"
}
] |
code_release-notes_d4fdf29a
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-03/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - March 2020\ndescription: \"See what is new in VTEX IO for March 2020\"\ndate: \"2020-04-15\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-03/README.md\"\n---\n\n# VTEX IO Release Notes - March 2020\n\nWelcome to the March 2020 VTEX IO Release Notes, team.\n\nWe've a difficult few days but **together we'll make it**. April is finally here, and with it the hope of positive change and a brand new Release Notes, straight from our world famous oven of ideas :bulb:\n\nLending credence to the idea the March was not all bad news, we've prepared a Release Notes to show what our team has been up to and to brighten these gray, lonely days a bit.\n\nSo wash your hands, sing Happy Birthday twice and cast your eyes on this beauty:\n\n## Features :rocket:\n\n- **Product Gifts app** - A brand new app to display all gifts available to a given product in your catalog. Check out the [documentation](https://vtex.io/docs/components/all/vtex.product-gifts@0.2.0/) and implement this in your store today! \n\n- **Product Price app** - The [product price block](https://vtex.io/docs/components/all/vtex.store-components/product-price), as we knew it from Store Components app, is now brand new and much more flexible in a new app called Product Price. Give the [documentation](https://vtex.io/docs/components/all/vtex.product-price@1.2.1/) a good read and implement the various blocks that are exported by this app with just a few clicks. \n\n- **Checkout UI Settings app** - Forget the admin's interface: the new Checkout UI Settings app is here to customize your VTEX IO store's Checkout UI through scripts. Get to know more about its advantages and inner workings by reading the [documentation](https://vtex.io/docs/apps/functional/vtex.checkout-ui-settings@0.0.3). \n\n- **Configurations Builder** - A service app's configurations can now be allocated as an independent app on the platform, leveraging from the functionality of workspaces, versioning and much more. It may seem complex, but it's not. Have a look at the documentation on how to use the builder to [develop service configuration apps](https://vtex.io/docs/recipes/development/developing-service-configuration-apps/). \n\n## Improvements :heavy_plus_sign:\n\n- **`menu-item` block from Menu** - The `menu-item` block is not a child composition, which means that menu items don't require a limited list of potential blocks that can declared as their children anymore - as mentioned in the [January 2020 Release Notes](https://vtex.io/docs/releases/2020-01/README/). Due to this change, `menu-item`s can henceforth declare any other Store Framework block in their array as children, granting more [Menu](https://vtex.io/docs/components/all/vtex.menu@2.24.1) customization. \n\n- **CSS Handles** - New CSS Handles available for the [Search Result](https://vtex.io/docs/components/all/vtex.search-result@3.53.1)'s `filter-navigator` v3 and for the Store Components' [`sku-selector`](https://vtex.io/docs/components/all/vtex.store-components@3.109.0/sku-selector)! Don't forget to check the CSS Handles table for each documentation!\n\n- **URL structure** - Most of the `map` parameters were removed from URLs, aiming to empower SEO on the platform. Only the `b` parameter was kept on the `map`, due to potential ambiguities between brands and categories. If previously we had something like `storecomponents.myvtex.com/shirts/t-shirts/green/Womens?map=c,c,c,specificationFilter_149,specificationFilter_151`, now we have `storecomponents.myvtex.com/shirts/t-shirts/for-whom_Womens/color_green`. Now this is what I call an improvement, team! \n\n- **Login** - New `accountOptionLinks` and `termsAndConditions` props for the area responsible for displaying specific account option links to replace the `My Account` and a markdown text below the login options to warn users about Terms & Conditions, respectively. Both are also editable using the admin's Site Editor! Whoopi-ty-doo! Check the [Login app documentation](https://vtex.io/docs/components/all/vtex.login/) for more info on each change.\n\n- **Slider Layout** - `fullWidth`, `autoplay` and `itemsPerPage` props are now available for edition using the admin's Site Editor. Each respectively: 1) defines whether the slides take up the full available width or not; 2) controls the auto-play feature; 3) defines how many slides should be displayed on each device. Access the [documentation](https://vtex.io/docs/components/layout-blocks/vtex.slider-layout@0.11.0/) for more info on each one!\n\n- **Filter Navigator** - The `initiallyCollapsed` prop, which was only accepted by the `filter-navigator.v2`, can now also be configured using `filter-navigator.v3`! Check the [Search Result app documentation](https://vtex.io/docs/components/all/vtex.search-result@3.55.2/).\n\n- **Performance improvements** - We have a significant performance increase for you due to platform changes. The first is related to the [Locale-Switcher](https://vtex.io/docs/components/all/vtex.locale-switcher@0.5.5/). The app and its blocks are now loaded only when under direct interaction with users, thereby decreasing page loading time. The second refers to the Order Form optimization. You can now optimize how your store fetches and uses the Order Form and therefore ensure a smoother navigation experience for your users. If this peaked your interest, have a look at the recipe on [**enabling the Order Form optimization**](https://vtex.io/docs/recipes/store-management/enabling-order-form-optimization/).\n\n- **Store Form** - While the Store Form was incredible and wonderful before, the JSON Schema compatibility was restricted to [Master Data v2](https://help.vtex.com/tutorial/master-data-v2--3JJ1mlzuo88w22gO0gy0QS). Water under the bridge. Thanks to this release, users can now create JSON Schemas that are compatible with Master Data v1 as well! Check out the [documentation](https://vtex.io/docs/components/all/vtex.store-form@0.3.4/).\n\n- **Outline-color** - The `outline-color` CSS property was added to your theme's `style.json` file. It means that you can set a unique default value that can be applied throughout the store for the line that is drawn around all components when they are highlighted on the interface. Previously, you could only set the component's customization in focus individually [using Handles](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization).\n\n## Bug Fixes :bug:\n\n- **Duplicated blocks**: Store Framework was passively accepting a block being declared twice in your store's theme (as long as one was a `.json` file and the other a `jsonc`). This led to various bugs, since only one of the two was going to be effectively rendered... but the developer didn't know which one. An error message is now displayed in Toolbelt whenever the theme is linked and duplicate blocks are present. \n\n- **[Sensitive Menu](https://github.com/vtex-apps/menu/pull/91)**: It was easy to mistakenly change the Menu you were navigating on since the Hover was way too sensitive. This is now fixed and you can expect a better user experience when using the Menu. Check out the before and after below.\n\nPreviously:\n\n\n\nNow:\n\n\n\n- **[`utm_source` on orderForm](https://github.com/vtex-apps/add-to-cart-button/pull/12)** - The expected behavior is for the Add to Cart button to input the `utm_source` data (contained in the user's session) to orderForm, the JSON responsible for storing all the date of an order on the platform. Unfortunately, this was not being done before... but it is now. Cheers!\n\n- **[Specifications Badges](https://github.com/vtex-apps/product-specification-badges/pull/6)** - All the [Specifications Badges](https://vtex.io/docs/app/vtex.product-specification-badges@0.1.0) of a product must be made available to the user... however only the first one configured was being displayed. This fix changes that and now all badges are displayed accordingly.\n\n- **[Telemarketing functionality](https://github.com/vtex-apps/store-graphql/pull/451)** - When a Telemarketing user added products to the cart using a client's account and then switched accounts, the Minicart did not reset, meaning that the OrderForm JSON continued to save the information pertaining to the previous account. This has been fixed: the cart is reset and the OrderForm data is cleared every time the Telemarketing user logs out of an account.\n\n```"
}
] |
code_release-notes_30b828d4
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-38/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 38/2019\ndescription: \"See what is new in VTEX IO Week 38/2019\"\ndate: \"2019-09-27\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/README.md\"\n---\n\n# VTEX IO Highlights - Week 38/2019\n\nDid you ever imagine two VTEX IO Release Notes in one week? **we**. **are**. **on**. **fire** 🔥\n\nHope you will be able to set some time aside from your busy workweek to catch up with VTEX IO one more time.\n\nCheck out our key releases for week 38 of 2019 below:\n\n> :bell: Keep up with VTEX IO release notes! Just click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- [Fold block](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/fold-block.md) - 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!\n- [GraphQL types import](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/graphql-types-import.md) - Save your precious time while developing! From now on, easily import GraphQL types from one app to another.\n- [Product Customizer component](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/product-customizer-component.md) - ~(finally)~ Display product attachments in your product page using the Product Customizer component.\n\n### Improvements :heavy_plus_sign:\n\n- [Sandbox with OrderForm](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/sandbox-with-orderform.md) - The user's cart data can now be used in Sandbox components in a fast and simple way.\n- [New Toast CSS handle](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/new-toast-css-handle.md) - Customize the Toast component with a different style from the rest of the store thanks to the new CSS handle.\n- [Toast component redirect](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-38/toast-component-redirect.md) - 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.\n\n### Notable bug fixes :bug:\n\n- [Free products on Google Shopping](https://github.com/vtex-apps/store/pull/360) - Products are no longer being displayed as free on Google Shopping since the issue in our structured data that caused this bug was fixed.\n- [`i18n` key props](https://github.com/vtex-apps/admin-pages/pull/279) - 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.\n- [`__provideRuntime` cache](https://github.com/vtex-apps/admin-pages/pull/280) = 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.\n\n```"
}
] |
code_release-notes_b15bb51e
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-04/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - April 2020\ndescription: \"See what is new in VTEX IO for April 2020\"\ndate: \"2020-05-20\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-04/README.md\"\n---\n\n# VTEX IO Release Notes - April 2020\n\nThe VTEX IO Release Notes is here, team!\n\nThrilled to announce that this April's Release Notes brings a ton of beautiful releases to enlighten your cloudy days at home.\n\nLet me share an insider's tip with you: *schedule a time of your day to go through it all*... you don't want to get left behind on the **latest key changes on the platform**!\n\nGet a sneak peek at last month's releases:\n\n## Features :rocket:\n\n- [**Overlay Layout app**](https://vtex.io/docs/components/all/vtex.overlay-layout@0.1.2/) - A layout app that provides you blocks to create a dropdown, select or a tooltip component in your store. Sounds amazing and simple... and it actually is!\n\n- [**Condition Layout app**](https://vtex.io/docs/components/all/vtex.condition-layout@1.1.7/) - You now get to define different layouts for the same page. This one seems like magic but it's not: choose predefined conditions and have the power to decide if a block should be rendered or not.\n\n- [**Seller Selector app**](https://vtex.io/docs/components/all/vtex.seller-selector@0.1.0/) - Marketplace stores will really enjoy from this one: use this app and display the number of [sellers](https://help.vtex.com/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w) available for each product, enabling users to compare prices and add the desired product to their cart.\n\n- [**Quickorder app**](https://vtex.io/docs/components/all/vtex.quickorder@0.7.2/) - Designed for B2B scenarios, the Quickorder app is here to speed up buying processes by offering tools to process large orders in bulk.\n\n- [**Google Customer Reviews pixel app**](https://vtex.io/docs/components/pixel/vtex.google-customer-reviews@1.0.2/) - A native integration for [Google's service](https://support.google.com/merchants/answer/7124326?hl=en) that collects feedback from customers who’ve made a purchase on your site is now a couple configs away.\n\n- [**Cookiebot pixel app**](https://vtex.io/docs/components/pixel/vtex.cookiebot@2.0.1/) - The native integration for the [Cookiebot solution](https://www.cookiebot.com/) is live. This pixel app is responsible for that handling the privacy and cookie policy for your store.\n\n- [**Iubenda pixel app**](https://vtex.io/docs/components/pixel/vtex.iubenda@0.2.1/) - Three is a charm, isn't it? This pixel provides native integration with the [Iubenda solution](https://www.iubenda.com/en/?utm_source=adwords&utm_medium=ppc&utm_campaign=aw_brand_global_exact&utm_term=iubenda&utm_content=336331123145&gclid=EAIaIQobChMI-ufW1Yid6QIVEYGRCh1zHAmFEAAYASAAEgLP_fD_BwE) that also handles the privacy and cookie policy for your store.\n\n- [**Trustpilot pixel app**](https://vtex.io/docs/components/pixel/vtex.trustpilot@1.0.2/) - Yep, that's right. Fourth pixel app of the evening. This one is for a native integration with the [Trustpilot solution](https://www.trustpilot.com/), responsible for providing your store with review and rating tools.\n\n- [**VTEX Intelligent Search**](https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb) - Get to know the VTEX Intelligent Search application for e-commerce. The new solution provides search components and a brand new Search Engine to assist customers during their purchase journey in VTEX IO stores. Take a look!\n\n## Improvements :heavy_plus_sign:\n\n- **Public app documentation** - Publish an app on the VTEX IO platform and win a public documentation slot in VTEX IO Docs! This functionality is not new, but its communication is: from now on, Toolbelt (version `2.101.0` or higher) will display the public documentation's link each time an app is successfully published!\n\n- **Toolbelt's commands** - The VTEX IO CLI has undergone an improvement: now, every command has its own `--help` flag. When running `vtex {commandName} --help` in the terminal, you can expect the command's documentation to be shown! \n\n- **CSS Handles** - Let's talk about good news related to [CSS Handles](https://vtex.io/docs/recipes/style/using-css-handles-for-store-customization) for the [Rich Text](https://vtex.io/docs/components/all/vtex.rich-text@0.10.0/) (`tableTr`, `tableTh` and `tableTd`), [Drawer](https://vtex.io/docs/components/all/vtex.store-drawer@0.12.1/) (`opened`, `closed` and `moving`) and the Filter Navigator block (`filtersWrapper` and `filtersWrapperMobile` ) from the [Search Results](https://vtex.io/docs/components/all/vtex.search-result@3.59.0/) app.\n\n- **Product Quantity's unit measurements** - The [Product Quantity app](https://vtex.io/docs/components/all/vtex.product-quantity@1.4.1/) now works with different unit measurements... that's right. Previously, the component would only display products by number of `units`. Now, the default for the new component is to always effortlessly display the product's defined measurement unit, such as `kg`.\n\n- **Modal Layout triggering** - No more repeated content: the modal content displayed from the [Modal Layout](https://vtex.io/docs/components/all/vtex.modal-layout@0.4.2/) app can now be triggered just once during the user session thanks to the new `trigger` prop.\n\n- **Aspect Radio on Product Summary Images** - The [Product Summary Image](https://vtex.io/docs/components/all/vtex.product-summary@2.54.1/product-summary-image/) block has two new props (`maxHeight` and `aspectRatio`) that help display your images in a uniform manner, irrespective of their original size. \n \n- **`search-products-progress-bar` block** - The [Search Results](https://vtex.io/docs/components/all/vtex.search-result@3.59.0/) app now has a new block called`search-products-progress-bar`, which is responsible for displaying a progress bar indicating the total amount of products fetched in the search comparing to the amount being displayed on the page.\n\n- **Sandbox URL** - When using a [Sandbox](https://vtex.io/docs/components/all/vtex.sandbox@0.5.0/) component, it is now possible to open a URL in the same browser tab in which you are navigating.\n\n*Still with us? I hope so, my friend, because our team wasn't fooling around in April...*\n\n- **`back-to-top-button` block** - Brand new [`back-to-top-button`](https://vtex.io/docs/components/all/vtex.store-components@3.114.6/backtotopbutton/) block from the Store Components app redirects users to the top of the page when clicked on. \n\n- **Query strings in the Store Link's URLs** - Say hello to query string attributes in the [Store Link](https://vtex.io/docs/components/all/vtex.store-link@0.5.1/) blocks! These are now allowed in the URLs used by the component.\n\n- **Event Configurations** - In the [Release Notes for March](https://vtex.io/docs/releases/2020-03/README/), we announced that the Configurations builder allows you to [develop service configuration apps](https://vtex.io/docs/recipes/development/developing-service-configuration-apps/) mainly through routes. Now, the Builder also works with events, which means that you can use the last one to add configurations in your service app.\n\n- **`product-spot-price` block** - The [Product Prices app](https://vtex.io/docs/components/all/vtex.product-price@1.3.0/) just got lucky and gained a new block responsible for rendering the product spot price (the `product-spot-price`) if this price differs from the product selling price.\n\n- **Infocard markdown texts** - Good news: [Infocard block](https://vtex.io/docs/components/all/vtex.store-components@3.114.6/infocard/) has a new prop called `textMode` that supports markdown texts in bold and italic!\n\n- **Infocard links** - Another one for the [Infocard](https://vtex.io/docs/components/all/vtex.store-components@3.114.6/infocard/): the new props `callToActionLinkTarget` and `linkTarget` allow you to control whether the block's links will redirect users to a new browser page or not.\n\n## Removals :no_entry:\n\n- **`vtex install` command** - The `vtex install` command underwent changes to improve the installation flow of apps: now, whenever both version's major and minor have been defined through the command, you'll need to also define the desired patch, meaning that commands such as `vtex install vtex.render-server@8.0.x` won't be able to install the app. To know more about how to properly install an app using Toolbelt, check out our documentation on [installing an app](https://vtex.io/docs/recipes/development/installing-an-app/).\n\n## Notable bug fixes :bug:\n\n- [**Mobile Filter Navigator**](https://github.com/vtex-apps/search-result/pull/334) - A 'close' button was missing by mobile users in the `filter-navigator` block . Now, that button is present once again and users are able to apply or clear filters and finally close the filters window.\n\n- [**Quantity Selector on Shelf**](https://github.com/vtex-apps/product-quantity/pull/13) - The Quantity Selector from the [Product Quantity app](https://vtex.io/docs/components/all/vtex.product-quantity@1.4.1/) was not working when displayed on a Shelf. Although users were choosing a desired quantity for a certain product, this was not being reflected in the Minicart. Now, everything is working as it should.\n\n## Praises :sparkles:\n\nWe would not be able to deliver so many amazing results during this last month if it were not for the following outstanding contributors:\n\n- [BeatrizMiranda](https://github.com/BeatrizMiranda)\n- [felipeireslan](https://github.com/felipeireslan)\n- [leoWorkingGood](https://github.com/leoWorkingGood)\n- [Lucasayb](https://github.com/lucasayb)\n- [marcosewbank](https://github.com/marcosewbank)\n- [rayra-alencar](https://github.com/rayra-alencar)\n\nThank you, team! :muscle:\n\n\n```"
}
] |
code_release-notes_dd9ac3ed
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-47-48-49-50-51/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - December 2019\ndescription: \"See what is new in VTEX IO December 2019\"\ndate: \"2019-12-19\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-47-48-49-50-51/README.md\"\n---\n\n# VTEX IO Release Notes - December 2019\n\nYou better watch out, you better not cry, you better not pout and I'm telling you why: **Release Notes** (once again) **is coming to town**!\n\nGiven the holiday's never ending glee (and the 117 Fahrenheit if you're in Brazil :sun_with_face:) that December bestows upon us all, the **Christmasy Release Notes** comes in an exclusive format this last month of the year, bringing the best and latest of the past few weeks.\n\nYou can call me Santa Claus 'cause once you've read everything you'll feel like you've just found a Christmas tree loaded with **goodies** :christmas_tree: There are so many amazing releases bundled together that I bet you'll go through them as fast as **2019** went by...\n\n### New features :rocket:\n\n- [Reviews and Ratings](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/reviews-and-ratings) - Finally! A product review and rating solution to call our own!!! Say goodbye to the old third-party solution you were using and cast your eyes on this new release.\n- [Publish command](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/publish-command) - If you take a deep breath, you can catch a whiff the A/B tests in the air. That’s because the Publish command from 01/02/2020 on will change its functionality and more steps will be added to the process of publishing an app on the platform. Everything to say goodbye to potential instabilities and to foster a culture of tests among our beloved devs.\n- [Challenge Trade Policy Condition](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/challenge-trade-policy-condition) - This release was so necessary that you don't even have to be into B2B to rejoice with us: now, you can establish conditional rules to determine whether a user can or cannot access the content of a given trade policy.\n- [Blocks on Site Editor](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/blocks-on-site-editor) - We won't deny it... we love it when the Site Editor has a new release. This one's amazing: three more of your store's components can be edited using the Site Editor's admin: Search Bar placeholder, Minicart Icon Label and Product Description title.\n\n### Deprecation :x:\n\n- [Declaring blocks stemming from indirect dependencies](https://vtex.io/docs/releases/2019-12-12/declaring-blocks-stemming-from-indirect-dependencies) - This one was already released and announced, but it's worth letting the crew know once more: Store Builder now requires all blocks that are used in the construction of a store's theme to be defined by the app's direct dependencies, meaning that declaring blocks stemming from indirect dependencies is no longer allowed.\n\n### Improvements :heavy_plus_sign:\n\n- [SKU Selector](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/sku-selector) - Retailers always want power and control over their blocks. Not that I'm judging them, since they're more than right to want as much flexibility as possible for their stores. Therefore, meeting demand, new SKU Selector props (`initialSelection` and `displayMode`) are now here to get rid of block rigidity.\n- [Minicart](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/minicart) - If there is one thing that a store can always improve upon, it's user experience. The new Minicart `openOnHover` prop is here to make that point.\n- [CSS Handles](https://vtex.io/docs/releases/2019-week-47-48-49-50-51/css-handles) - We get a fuzzy feeling inside whenever a CSS Handles release is nearby! Have a look at our blocks that gained new Handles and are ready to be fully customized: Menu, Flexible Search Result and Product Price.\n\n### Notable bug fixes :bug:\n\n- [Brands on Product Related Shelf](https://github.com/vtex-apps/shelf/pull/199) - The Product Related Shelf product brands were not rendered in the same way as the classic Shelf products. This fix removed this Brand ID preference. Product brand now appear on Product Related Shelves as well, without being discriminated against.\n- [Active thumbnail on Product Image](https://github.com/vtex-apps/store-components/pull/641) - The CSS Handle `active`, responsible for customizing thumbnails of images that were selected in the Product Details Page, was ignoring the thumbnail selection. Oh my dear `active`, you had but one job to do! The Handle was only keeping the configured customization for the first image on the list, even if users had selected another image. This has come to an end and the customization now respects the user's power of choice. Hoo-rah!\n- [Filter clearing on Mobile](https://github.com/vtex-apps/search-result/pull/283) - What purpose does the `Clear` button serve on a Filter? Clearing all the applied filters, right? But it seemed that `Clear` was the only one not understanding that. The button didn't clear anything, leaving users with the same active filters as before. With this bug fix, the `Clear` button now does what it was meant to do.\n- [Filter Sidebar on Mobile](https://github.com/vtex-apps/search-result/pull/282) - When choosing the desired filters for mobile and clicking on `Apply`, the sidebar remained open without serving any purpose to users. If there was bug to be fixed there, it seems it had to do with the mobile Filter. It's now perfect for use: the sidebar's behavior was remedied and it's now closing as expected after clicking on `apply`.\n- [Bazaar Voice](https://github.com/vtex-apps/bazaarvoice/pull/24) - Previously, the Bazaar Voice was failing to properly function for the `trackTransaction` event. This led to prices not being sent correctly and to lack of visibility for retailers. How very sad! Everything's back to blossoming for the Bazaar Voice review and sent prices.\n\n---\n\nWords cannot express how glad we are to have you with us on this journey!\nHere's to next year and to the incredible releases that awaity :beers:\n\n**Happy Holidays!**\n\n```"
}
] |
code_release-notes_07e56735
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-11-12/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - November&December 2020\ndescription: \"See what is new in VTEX IO for November&December 2020\"\ndate: \"2021-01-15\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-11-12/README.md\"\n---\n\n# VTEX IO Release Notes - November&December 2020\n\nWeep no more, team: here we (*finally*) are :tada:\n\nLet's make room for the VTEX IO Release Notes, this time around bringing you double the excitement from last November and December! \n\nIf 2020 made us shed some tears, our VTEX IO team worked around the clock to bring a smile back on our faces :grin: Just look at the awesome stuff they've delivered as last year came to an end: \n\n- 🚀 Condition Layout v2\n- ➕ Importing private CSS Classes\n- ⚠️ Unannotated queries requested as public\n- 🐛 Search results with special characters\n\nAnd unlike 2020, things are looking up, okay? In addition to the tremendous deliveries the team had, we also have a **special announcement** regarding IO Docs and the **migration of our documentation to the Developer Portal**.\n\nBelieve me when I say it... you can't sit this one out! Without further ado, introducing the one and only VTEX IO Release Notes:\n\n## Special announcement :speaker:\n\n- **New home for the VTEX IO documentation**\n\nOfficially housing VTEX IO documentation since September, 2019, IO Docs was the successful result of VTEX's effort to create a more in-depth and narrowly focused documentation.\n\nWith almost a year gone by, it's time to say goodbye: to better take advantage of existing and future VTEX IO documentation and to leverage the development experience of our users, **VTEX IO documentation will henceforth be stored on our [Developer Portal](https://developers.vtex.com/), starting today (January 15, 2021)!**\n\n> :information_source: *All existing documentation will be redirected and automatically migrated to the new platform. No existing link will be lost during this process.*\n\n\n\nHome to our [API documentation](https://developers.vtex.com/reference) and [guides](https://developers.vtex.com/docs) aimed at developers working with integrations and customization, the [**Developer Portal**](https://developers.vtex.com/) - formerly known as Help Center Developer Docs - offers all the necessary resources for VTEX's most advanced users in a single place.\n\nSuch changes to the VTEX IO documentation mean a lot more than just content redistribution, trust me: they will ensure a **better and greater support for VTEX IO users** and their specific objectives on our platform.\n\nAs to the future of our beloved Release Notes, don't worry: in addition to the [Developer Newsletter](https://forms.gle/DHo3SS7ZaGCvAMow8) bringing you all the essential updates on platform changes, the Developer Portal also has its own Release Notes section:\n\n\n\nNothing but the address will change, I promise! Everything else stays the same, with the same high-quality impactful content, working together as always, but now housed in a place that can fully encourage our potential :sparkles:\n\n## Features 🚀\n\n- **Condition Layout v2** - What is better than the Condition Layout v1? Its second and most optimized version, of course! Welcome the Condition Layout v2, bringing you features such as verification by product specification value and product availability. Learn more about the new version by checking out the new [documentation](https://vtex.io/docs/components/all/vtex.condition-layout/) and the specially-prepared [migration guide](https://github.com/vtex-apps/condition-layout/blob/master/docs/MIGRATION-GUIDE.md)!\n\n- **Native integration between the Subscription module and the front-end** - Forget the messy old days when you had to develop a custom app to manage subscriptions on the front-end! The Product Customizer app is now natively compatible with the [Subscription module](https://help.vtex.com/en/tutorial/how-subscription-works--frequentlyAskedQuestions_4453), meaning you are now able to edit the name and the frequency of a product subscription through the store component in the product details page. Access the [Product Customizer app documentation](https://vtex.io/docs/components/all/vtex.product-customizer/) now to get more details of this new feature! \n\n\n\n- **The `product-reference` block** - Let's greet the new `product-reference`, exported by the Product List app! The block is responsible for rendering product reference data onto components that leverage from its app, such as the [Minicart](https://vtex.io/docs/components/all/vtex.minicart/). Do we have your attention? Do not forget to cast your eyes on the [documentation](https://vtex.io/docs/components/all/vtex.product-list/) for more details!\n\n - **Google Customer Review badge** - The Google Customer Reviews pixel app now counts on a new component to enrich your store's front-end: we're talking about the `google-customer-review-badge` block, which renders the Google Customer Review icon to the UI! Check out the [docs](https://vtex.io/docs/components/pixel/vtex.google-customer-reviews/) to better understand how to set it up!\n \n- **Enabling automatic translation in the Messages app** - Safely and quickly enable or disable automatic Messages app translations directly from your VTEX admin account, as highlighted in the screen grab below! But please note: the toggle only defines the configuration for automatic translations, not for manual ones. If you need more info, access the recipe on [Disabling automatic translation](https://vtex.io/docs/recipes/store-management/disabling-automatic-translation/)!\n\n\n\n## Improvements ➕\n\n- **Importing private CSS Classes** - Avoid external editions and customize your store components using private CSS classes i.e. classes whose name contains a hash (unique identifier) instead of the traditional `vendor-app-major-x-classname` format that is generated when importing. For more info on how to import CSS classes (private or public, as we call the ones with the traditional format), access our documentation on [Defining styles](https://vtex.io/docs/getting-started/desenvolva-componentes-usando-vtex-io-e-react/5/)! \n\n- **Dynamic routes customization on CMS** - Customizing dynamic routes can now be done through the admin's CMS, thanks to a wonderful new update to the [Pages GraphQL](https://github.com/vtex/pages-graphql/releases/tag/v2.103.0). For more on the possibilities of this customization, access this [documentation](https://vtex.io/docs/recipes/templates/associating-a-custom-page-to-a-content-type/)!\n\n- **Catalog translation by variable** - Translating a store's catalog can be done in the blink of an eye thanks to this improvement which makes it possible to translate the desired catalog data simply by filling in the specific variables in the object of the GraphQL API. Previous translations were only enabled when all the object's variables were filled in. Caught your attention? Have a closer at our documentation on [catalog internationalization](https://vtex.io/docs/recipes/store-management/translating-catalog-content)! \n\n - **Placeholders on the Store Form component** - Thanks to the new `placeholder` prop, added to the `form-input.textarea` block, the [Store Form](https://vtex.io/docs/components/content-blocks/vtex.store-form/) component now accepts placeholders for text inputs, meaning that from now on you can add descriptions as well as other desired instructions to the form's text fields.\n \n\n \n- **Link building in the product brand's name** - A new prop has arrived for the [`product-brand` block](https://vtex.io/docs/components/all/vtex.store-components/product-brand) from the [Store Components app](https://vtex.io/docs/app/vtex.store-components/): the `withLink`! Replacing the former `logoWithLink` prop, the new one is here to help you create links for the product brand's website based on text strings or image icons. \n\n\n\n*take a deep breath, we're half way through already... it's been two whole months! There's a lot where that came from! Check it out:*\n\n- **Multiple gallery layouts** - Having multiple layout configurations for your search results page may sound impossible, but thanks to the Search Result's `gallery-layout-switcher` and `gallery-layout-option` new blocks, it is not! To learn how to customize the page, check out the [Building a search results page with multiple layouts recipe](https://vtex.io/docs/recipes/templates/building-a-search-results-page-with-multiple-layouts/)!\n\n\n\n- **Multiple seller compatibility** - The [Add To Cart Button](https://vtex.io/docs/components/all/vtex.add-to-cart-button/), [Buy Button](https://vtex.io/docs/components/all/vtex.store-components/buy-button) and [Product Price](https://vtex.io/docs/components/all/vtex.store-components/product-price) now use as their default behavior the first *available* seller's data, meaning they are able to work with multiple seller data. Previously, the components only worked with the first seller's data, regardless of their availability and ignoring the rest of the seller list - tricky, wasn't it? now, this is what our team calls an improvement! \n\n- **Product image placeholder** - From now on, set a default image as placeholder for your store products thanks to the new `placeholder` prop, available for the [`product-images`](https://vtex.io/docs/components/product/vtex.store-components/product-images/) and [`product-summary-image`](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-image) blocks, respectively from the [Store Components](https://vtex.io/docs/app/vtex.store-components/) and the [Product Summary](https://vtex.io/docs/components/all/vtex.product-summary/) apps. \n\n- **Product list identification on Google Analytics** - Thanks to the new `listName` prop added to the [`product-summary-list` block](https://vtex.io/docs/components/all/vtex.product-summary/product-summary-list/), part of the [Product Summary](https://vtex.io/docs/components/all/vtex.product-summary/), and additional improvements made to the [Tag Manager](https://vtex.io/docs/components/all/vtex.google-tag-manager/)'s `productClick` event, you can now identify which store shelf users interacted with. No more misleading results for the poor Analytics!\n\n- **Close drawer on the UI** - A new `text` prop was added to the `drawer-close-button` block, part of the [Drawer app](https://vtex.io/docs/components/all/vtex.store-drawer/), responsible for closing components on the UI. Thanks to it, you can now close the Drawer using a text button, instead of the traditional `X` icon. \n\n- **The `promoView` and `promotionClick` events** - New events for the [Google Tag Manager pixel app](https://vtex.io/docs/components/all/vtex.google-tag-manager/). Best of all? They all follow the official google enhanced commerce format! Please welcome the [`promoView`](https://developers.google.com/tag-manager/enhanced-ecommerce#promo-impressions) and the [`promotionClick`](https://developers.google.com/tag-manager/enhanced-ecommerce#promo-clicks) events, responsible for displaying a store's promotion impressions. \n\n\n\n## Warnings ⚠️\n\n- **Unannotated queries requested as public**\n\nThe fallback cache option for GraphQL queries that didn't have an annotation on cache policy (`@cacheControl`) has changed from the **default public scope to the private** instead, in order to solve an internal issue on the platform. \n\nAlthough it does not affect functionality, this can impact the store front's performance due to changes to the queries essence, since all unannotated that were being requested as public are now automatically coming in as private.\n\nOur team advises developers that have created custom VTEX IO GraphQL services to closely review their schemas and, if necessary, add the `@cacheControl(scope: PUBLIC)` directive for the unannotated queries. This [Pull Request](https://github.com/vtex-apps/store-graphql/pull/516) should illustrate how to code the workaround solution.\n\n## Bug fixes 🐛\n\n- [**Displaying modals according to URL changes**](https://github.com/vtex-apps/modal-layout/pull/43) - Previously, modals were not automatically closed according to changes in the URL, meaning that they were kept open regardless of the user's navigation. The question is: was it the best behavior our component could have for our users? We all know the answer to that, so it is time to celebrate: this behavior was fixed and modals are now automatically closed whenever changes to the URL occur.\n\n- [**Empty-label validation on Tab Layout**](https://github.com/vtex-apps/tab-layout/pull/16) - Still thinking of enhancing user experience, the Tab Layout app will from now on only display tabs (i.e. the `tab-list.item` blocks) whose `label` props has been properly filled out. In practice, it is safe to say that it is the end of empty tabs being displayed on the UI! Cheers to that!\n\n- [**Product ordering in the `productImpression` event**](https://github.com/vtex-apps/product-list-context/pull/10) - The `position` field, part of the `productImpression` events, was not being properly filled out with the real positioning of listed products. An accurate ordering is now taken into account by our Product Context and this bug is (praise the Lord) fixed!\n\n- [**Search results with special characters**](https://github.com/vtex-apps/store-graphql/pull/503) - Forget about the times when no results were fetched for searches with special characters: due to this magical fix, the Search Result's search bar is more cooperative, meaning that results are now properly displayed regardless of the special characters used to fetch them.\n\n- **`productImpression`'s threshold** - The Google Tag Manager's `productImpression` event was only triggered when 75% or more of the Product Summary component was displayed. This type of threshold for sending data resulted in misleading results to the GTM, since Product Summaries are usually displayed as carrousels of many products and slides. With this bug fix, the `productImpression` event no longer has a threshold, being sent out as soon as the Product Summary is visible on the UI. \n\n## Praises ✨\n\nWe would not be able to deliver so many amazing results during these last two months if it were not for the following outstanding contributors:\n\n- [Wesly Souza](https://github.com/weslybrandao) *from ACCT*\n- [Gustavo Vasconcellos](https://github.com/gustavopvasconcellos) *from ACCT*\n- [Lucas Castro](https://github.com/LucasCastroAcctGlobal) *from ACCT*\n- [Matheus Araujo](https://github.com/MatheusR42) *from Corebiz* \n- [Renan Guerra](https://github.com/renanguerraa1) *from ACCT*\n- [Luiz Eduardo](https://github.com/LEduard0)\n- [Pmarignan](https://github.com/pmarignan)\n\nThank you, team :muscle:\n\n```"
}
] |
code_release-notes_496d1698
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-41-42/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - Week 41&42/2019\ndescription: \"See what is new in VTEX IO Week 41&42/2019\"\ndate: \"2019-10-25\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-41-42/README.md\"\n---\n\n# VTEX IO Release Notes - Week 41&42/2019\n\nHey team! One more VTEX IO Release Notes coming your way.\n\nIn tune with the Halloween spirit, quick disclosure: more so than ghosts and zombies, my worst fear is not knowing what is going on with VTEX IO 😨 I'm betting you dread the same thing!\n\nTherefore, take a deep breath, relax and banish your fears, because we have a new Release Notes and it's full of delicious treats:\n\n### New features :rocket:\n\n- [Responsive Layout](https://vtex.io/docs/releases/2019-week-41-42/responsive-layout) - Should we start calling ourselves the gods of layout components? The Responsive Layout allows different layouts per breakpoint! It is so awesome and versatile that you'll think it's really godlike.\n- [New way to create CSS Handles](https://vtex.io/docs/releases/2019-week-41-42/css-handles-component-development) - Devs, celebrate with me: this release is about a more advantageous, easy and brand new way to create CSS Handles for store components.\n\n### Deprecation ❌\n\n- [Infinite scroll on the flexible search results page](https://vtex.io/docs/releases/2019-week-41-42/infinite-scroll-on-flexible-search-result-page) - No one wants a bad UX, right? Therefore, this deprecation is already deployed and you'll now understand why.\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://vtex.io/docs/releases/2019-week-41-42/platform-performance) - Understand what were the VTEX IO performance improvement key points for week 41 and 42 of 2019.\n- [CSS Handles](https://vtex.io/docs/releases/2019-week-41-42/css-handles) - If you just knew just how much effort our team is putting into making CSS Handles a reality for all store components, you would go to sleep dreaming about CSS Classes. Check out our latest CSS Handles releases!\n- [SKU Selector](https://vtex.io/docs/releases/2019-week-41-42/sku-selector) - New SKU Selector props that will allow you to define image height and width without needing to resort to CSS customization. Enhanced performance and practicality in a single improvement: a dream come true.\n- [Product Summary](https://vtex.io/docs/releases/2019-week-41-42/product-summary) - Did you enjoy the SKU Selector release? So check out our Product Summary release as well: more props to define image sizes!\n\n### Notable bug fixes :bug:\n\n- [Buy Button redirect](https://github.com/vtex-apps/product-summary/pull/192) - The Buy Button should redirect the user to the PDP regardless of the SKU availability, since users must always know which SKU they are adding to the cart, right? But this wasn't what the button was doing before this fix! It added an SKU to the user's cart, by itself.\n\n- [Price Range loading](https://github.com/vtex-apps/search-result/pull/253) - Any change to the Price Range by the user now triggers a reload symbol, providing a better UX. In addition, the search result pagination now resets when any change to the component is performed. Before this bug fix, these two scenarios were not a reality... how awful!\n\n- [`mailto` and `tel` tags in Menu Item]() - When editing your store's content with Site Editor, you might have come across the `tel:` and `mailto:` tags that could not be read as `href` in a menu item. Now, they are working as originally intended! At long last!\n\n- [Tablet layout grid](https://github.com/vtex-apps/search-result/pull/255) - The Search Result component layout dimensions were not responsive to Tablet devices. They took on mobile dimensions, leading to content decentralization and very weird blank columns on the screen. This layout bug has been fixed.\n\n- [Similar categories in Breadcrumb](https://github.com/vtex-apps/search-graphql/pull/12) - Similar categories to those of the product were being displayed in the Breadcrumb component. Nothing against similar categories, but Breadcrumb isn't the place for that, right? Only the main category tree is now displayed in the component, due to data being fetched in the product's `categoryId`.\n\n- [Image thumbnail gallery arrows in PDP](https://github.com/vtex-apps/store-components/pull/604) - On the Product Details Page, arrows in product thumbnail images were broken when in horizontal mode. These only worked correctly in vertically displayed images! The arrows now understand that they should properly function in both display directions and this bug has been fixed.\n\n- [Site Editor infinite loading](https://github.com/vtex-apps/admin-pages/pull/292) - To allow users to edit a store's blocks using an interface, Site Editor needed to query the code's up-to-date data. Whenever this query encountered an error, the loading symbol was forever displayed to the user, which became confused, poor soul! The loading has now been replaced with an error message, improving the Site Editor UX.\n\n```"
}
] |
code_release-notes_c62599b1
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-25/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 25/2019\ndescription: \"See what is new in VTEX IO Week 25/2019\"\ndate: \"2019-06-26\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-25/README.md\"\n---\n\n# VTEX IO Highlights - Week 25/2019\n\nWelcome to the first VTEX IO weekly release notes!\n\nSince that is our first one, we have a large backlog of changes to communicate. 🚀\nThe following key changes were not necessarily done in the last week, but in the last couple of months.\n\n> 🔔 Keep up with VTEX IO release notes! Just click on <strong>Releases only</strong> in the <strong>Watch</strong> box on the right upper corner of this page.\n\n### Breaking changes ⚠️\n\n- [Custom HTML tags are now blocked from running on Google Tag Manager app](custom-html-tags-are-now-blocked-from-running-on-google-tag-manager-app.md) - Check how you should integrate your store with a third party service using a pixel app.\n\n### Deprecations ❌\n\n- [Global Messages discontinued](global-messages-discontinued.md) - Understand why Global Messages will be deprecated with the new version of the Web Framework.\n\n### New features 🚀\n\n- [Compatibility with Microsoft Edge Browser](compatibility-with-microsoft-edge-browser.md) - Build a store using the Store Framework v2 and run it normally on the Windows browser.\n- [B2B support](B2B-support.md) - Authenticate users in closed sales channels using the Search API.\n- [Product Review apps](product-review-apps.md) - Create your own Product Review apps with our abstract interfaces.\n\n### Improvements ➕\n\n- [SKU Selector component](sku-selector-component.md) - More than two SKU specifications can now be selected.\n- [Canoninal routes consistency](canonical-routes-consistency.md) - A new API was developed for canonical routes mapping.\n- [Typescript version consistent locally](typescript-versions-consistent-locally.md) - Local `package.json` is now overwritten with current Builder-hub's typescript version\n- [Shelf component](shelf-component.md) - Products from the same subcategory and the same specification can be shown up in a shelf.\n\n```"
}
] |
code_release-notes_62678b97
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2020-10/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Release Notes - October 2020\ndescription: \"See what is new in VTEX IO for October 2020\"\ndate: \"2020-11-24\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2020-10/README.md\"\n---\n\n# VTEX IO Release Notes - October 2020\n\nWhile Santa Claus is still not in town, the **VTEX IO Release Notes for October 2020** is the one in charge of delivering lots of goodies for you and delight your home-office days with :sparkles:*joy*:sparkles:!\n\nA tough ask, I know, since there is no end to this terrible and long-lasting virus in our gift basket, but I promise you that our team has prepared some rewards almost as long-awaited as that, such as:\n\n- 🚀 The new Store Locator app\n- ➕ Time optimization for hotfix deploys\n- 🐛 The fix in the `Add to cart` button performance\n \nCaught your attention? \n \nWhat a question... surely it did! Check out what October 2020 has brought us: \n\n## Features 🚀\n\n- **Blueknow pixel app** - A new pixel app is out of the oven for the [Blueknow solution](https://www.blueknow.com/en/), responsible for using big data techniques and digital merchandising to provide recovery of lost sales, onsite retargeting, customized recommendations, and more! Check out the [app documentation](https://vtex.io/docs/components/all/vtex.blueknow/) in order to learn how to set it up in your store!\n\n- **Kelkoo pixel app** - The more native integrations, the better: get ready for the [Kelkoo](https://www.kelkoogroup.com/) native integration! The new [pixel app](https://vtex.io/docs/components/all/vtex.kelkoo/) is here to help your store with incremental e-commerce leads!\n\n- **Store Locator app** - If adding information regarding pickup points to your store sounded complicated, it's water under the bridge! The Store Locator is among us to untie the knots in this setup - check out its [documentation](https://vtex.io/docs/components/all/vtex.store-locator/) now!\n\n\n\n- **Newsletter app** - Display a newsletter subscription form for your store users using the [Store Newsletter app](https://vtex.io/docs/components/all/vtex.store-newsletter/)! Leveraging from the former [Newsletter block](https://github.com/vtex-apps/store-components/blob/master/docs/Newsletter.md) (from the [Store Components app](https://vtex.io/docs/components/all/vtex.store-components/)), this latest and prettier one is here to let bygones be bygones and upgrade your store!\n\n\n\n- **Condition Layout v2** - The Condition Layout as we know was remodeled in order to achieve a clearer logic when setting the conditions to build your store's layout. In addition to its new [documentation](https://vtex.io/docs/components/all/vtex.condition-layout/), do not forget to access the [migration guide](https://github.com/vtex-apps/condition-layout/blob/master/docs/MIGRATION-GUIDE.md), specially prepared to help you with this upgrade!\n\n## Improvements ➕\n\n- **Time optimization for hotfix deploys** - The VTEX IO team has finally made it possible to warp time exactly as those kids from Dark did in order to deploy your hotfixes in less than 7 minutes! Using the Toolbelt's `2.118.0` version or newer, you can now run `vtex deploy --force` in your terminal when needed. But take note: the `--force` flag is only recommended for hotfixes! Normal deploys should use the `vtex deploy` as usual, since the 7 minutes are fundamental for testing your store's performance.\n\n- **CSS and GraphQL query optimization** - It's what I always say: If it contains performance improvements, then we can call it a good VTEX IO Release Notes! Glad to say that our team has worked really hard on CSS and GraphQL query optimizations and that these are already natively enabled in your store. For more info, check out our documentation on [best practices for optimizing performance](https://vtex.io/docs/recipes/store-management/best-practices-for-optimizing-performance/)!\n\n- **Store performance natively enabled** - If performance improvements are great and loved by everyone, shouldn't they be natively enabled? The VTEX IO team thinks the answer to that is a resounding yes! From now on, all new accounts using the platform will automatically inherit all the currently available store performance best practices. \n\n- **Sorting products by their collection** - Display products on your store's search results page according to the collection in which they were first sorted! Yep, that's right: the `order-by` block, part of the Search Result app, now works with products' colletions (`OrderByCollection`). Do not forget to learn more about it in the [Search Result documentation](https://vtex.io/docs/components/all/vtex.search-result/)!\n\n- **Error message for JSON parsing** - The lack of additional information was part of the developers' routine whenever something went wrong with parsing the app's JSON files. But not anymore: file and error line references will from now on be displayed in the error message.\n\n\n\n- **Render Runtime's typings** - These really are the glory days for VTEX IO developers: you can now count on a marvelous auto-complete feature in your IDE by running the `vtex setup --typings` command to add the Render Runtime's types to your app. For more info, check out the [Render Runtime documentation](https://github.com/vtex-apps/render-runtime)!\n\n- **Error message for Store Form's schema** - Error messages were added to the Store Form app in order to warn developers whenever the JSON schema was invalid, i.e. built with an inaccurate structure! What more can I say? It is safe to claim that the dog days are (*almost*) over for VTEX IO developers!\n\n - **Submenu navigation** - Opened submenus are now natively closed whenever another submenu is clicked/hovered on. Previously, the shift between submenus was so fluid that users were not able to notice when content changed - now that's what I call a smooth experience! This behavior was enhanced as shown below:\n \n\n\n- **Filters closing** - Let's make room for the new `closeOnOutsideClick` prop from the [Search Result](https://vtex.io/docs/components/all/vtex.search-result/)'s `filter-navigator.v3` block, responsible for defining whether the component should be closed with an outside click (as shown below) or not!\n\n\n\n- **Zendesk's chat button** - A new Zendesk's chat button was developed to lazy-load the default and heavier one provided by the solution. The replacement button, exported by the [Zendesk Chat pixel app](https://vtex.io/docs/components/all/vtex.zendesk-chat/), can add 15 and 30 points to your Lighthouse score for mobile and desktop devices, respectively. And it gets better: you can also customize the button in your account's admin page.\n\n- **Quantity Selector in dropdown mode** - The Quantity Selector block, exported by the [Product Quantity app](https://vtex.io/docs/components/all/vtex.product-quantity/), can now be rendered as a dropdown thanks to its new prop: the `selectorType`! \n\n\n\n- **Decimal place customization** - Customization is power and we do know that! CSS Handles were added to the product price's decimal places, allowing you to display them half a character above the normal line, and/or in a smaller font.\n\n- **Sitemap extension** - Shall we talk about *SEO* now? Your store's Sitemap can now be extended by other apps, meaning new files can now be natively added to the Sitemap's root XML. Want to know more? Access the [Store Sitemap app documentation](https://vtex.io/docs/components/functional/vtex.store-sitemap@2.13.3/) to keep up with the latest!\n\n## Bug fixes 🐛\n\n- [**`addToCart` event with inaccurate currency value**](https://github.com/vtex-apps/facebook-pixel/pull/16) - The `addToCart` event was displaying misleading data on product prices, harming Facebook tracking tools. The bug was quickly fixed and the currency values are now fetched as they ought to be!\n\n- **[Inconsistency between values in the Minicart](https://github.com/vtex-apps/checkout-summary/pull/38)** - The total value displayed in the Minicart was ignoring the value passed to the `totalizersToShow` prop, generating a mismatch between the values listed and their final sum. This crazy math was adjusted by our team and the total value now respects the vallue passed to the prop!\n\n- **Broken Product Quantity on IE11** - Internet Explorer 11 is one of the browsers supported by the Store Framework, but it seems to me that the [Product Quantity](https://vtex.io/docs/components/all/vtex.product-quantity/) component didn't get that until now... silly component! This disruptive behavior had been fixed and the component now works perfectly for IE11 users as well. \n\n\n\n- [**Unwanted product specifications being displayed**](https://github.com/vtex-apps/search-resolver/pull/115) - Although we have a checkbox in the Catalog module to set whether a specification should be displayed on the product details page or not, this info was not properly handled in our Product Specifications component. But not anymore: unwanted specifications are now blocked from being displayed when you select this option. This is what I call power of choice, my friends!\n\n- [**`Add to cart` button performance**](https://github.com/vtex-apps/add-to-cart-button/pull/50) - Shopping experience was being harmed because of the unexpected extra time needed to redirect users to the Minicart once the `Add to cart` button was clicked on. Our wonderful team deployed a series of performance fixes and small improvements, such as adding a native loading bar to the page, in order to enhance navigation during the shopping experience! \n\n- [**Product Highlights**](https://github.com/vtex-apps/product-highlights/pull/4) - The Product Highlights app misunderstood its concept and was displaying *all* collections as highlighted in the store. The undesired behavior was properly fixed, with the component now only displaying collections that have the highlight feature turned on!\n\n## Docs :page_facing_up:\n\nDocumentation is the **key**! Check out below our out-of-the-oven docs: \n\n### Recipes\n\n- [Consulting B2B order statuses](https://vtex.io/docs/recipes/store-management/consulting-b2b-order-statuses/)\n- [Safely enabling performance settings](https://vtex.io/docs/recipes/store-management/safely-enabling-performance-settings/)\n- [Indicating alternate versions of localized pages in cross-border stores](https://vtex.io/docs/recipes/store-management/indicating-alternate-pages-in-cross-border-stores/)\n- [Displaying asynchronous prices](https://vtex.io/docs/recipes/templates/displaying-asynchronous-prices/)\n\n### Concepts\n\n- [Properties](https://vtex.io/docs/concepts/properties/)\n- [Composition](https://vtex.io/docs/concepts/composition/)\n\n## Praises ✨\n\nWe would not be able to deliver so many amazing results during this last month if it were not for the following outstanding contributors:\n\n- [Julio Moreira](https://github.com/juliomoreira) *from B80ne*\n- [Gabriel Sampaio](https://github.com/gasampaiosouza) *from econverse*\n- [Gustavo Vasconcellos](https://github.com/gustavopvasconcellos) *from ACCT*\n- [Felipe Ireslan](https://github.com/felipeireslan) *from ACCT*\n- [khrizzcristian](https://github.com/khrizzcristian) \n- [mariusfiliutamindcell](https://github.com/mariusfiliutamindcell)\n\nThank you, team :muscle:\n\n```"
}
] |
code_release-notes_7159ddbe
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of release-notes/docs/2019-week-39-40/README.md from the release-notes VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```markdown\n---\ntitle: VTEX IO Highlights - Week 39&40/2019\ndescription: \"See what is new in VTEX IO Week 39&40/2019\"\ndate: \"2019-10-11\"\ngit: \"https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/README.md\"\n---\n\n# VTEX IO Highlights - Week 39&40/2019\n\nWelcome to the one and only VTEX IO Release Notes!\n\nI bet that you've missed us these past couple weeks, but weep no more 🤗\n\nNot only are we back, but we also have a proper explanation for turning off the lights for all this time: **the VTEX IO Release Notes will have a new format from now on, being published every two weeks**.\n\nNo need for the long face, team... a more extended publication time equals more time to bring together relevant content for you 🎉\n\nWithout further ado and with the given explanations, have a quick look at our key releases for weeks 39 and 40 of 2019:\n\n> :bell: Keep up with VTEX IO release notes! Just click on **Releases only** in the **Watch** box in the right upper corner of this page.\n\n### New features :rocket:\n\n- Store v2 Edition - No more headaches with manually installing `store` v2 compatible apps thanks to Store v2 Edition.\n- [Pickup Availability](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/pickup-availability.md) - New feature for strengthening Omnichannel experience? Oh yeah! Check out the new Pickup Availability component.\n- [Paging the Search Results](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/paging-the-search-results.md) - If agility is what you are searching for then this feature is for you. Now, the Search Results component provides a URL for each loaded search results page!\n- [Stack Layout](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/stack-layout.md) - Components overlapping other components. If this seems like something difficult, that's because you're unfamiliar with Stack Layout.\n- [Tab Layout](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/tab-layout.md) - What's better than one layout release? Two of them. The Tab Layout allow the construction of different layouts for your store's tabs.\n- [Product Specification Badges](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/product-specification-badges.md) - Specifications can define whether a user will or will not buy a certain SKU. Don't waste time and display them in badges with this new component!\n\n### Improvements :heavy_plus_sign:\n\n- [Platform performance](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/platform-performance.md) - Understand what the VTEX IO performance improvement key points were for week 39 and 40 of 2019.\n- [URL field auto-fill](https://github.com/vtex-apps/release-notes/blob/master/docs/2019-week-39-40/url-field-autofill.md) - When creating a new page in the admin's Page section, the URL field will automatically propose a path according to the page's chosen title. Isn't it just magical?\n\n### Notable bug fixes :bug:\n\n- [Negative discount badges](https://github.com/vtex-apps/store-components/pull/591) - The `DiscountBadge` component was displaying negative discount badges, such as -0%, when the product was being sold at a higher price than its original one. This strange behavior is now fixed and the `DiscountBadge` is not displayed if the product's discount is less than 1%.\n- [Attachment default values sent to Checkout](https://github.com/vtex-apps/product-customizer/pull/46) - Product attachment default values were being sent to checkout as if users had chosen them, even though they had not. This scenario no longer occurs.\n- [`tel:` Rich Text links attribute](https://github.com/vtex-apps/rich-text/pull/24) - Rich Texts can now interpret the HTML attribute `tel:` to create links for phone calls. Prior to this bug being fixed, this attribute was not interpreted (Rich Texts could only interpret the `mailto` attribute, used for sending e-mails).\n\n```"
}
] |
code_pleisty-integration_0dbbf9cb
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/index.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport { canUseDOM } from 'vtex.render-runtime'\nimport {\n Order,\n ProductOrder,\n PixelMessage\n} from './typings/events'\nimport { pleistyPush } from \"./utils/pleisty-utils\";\n\n\nexport function handleEvents(e: PixelMessage) {\n switch (e.data.eventName) {\n case 'vtex:orderPlaced': {\n const order = e.data;\n\n const ecommerce = {\n\n purchase: {\n actionField: getPurchaseObjectData(order),\n products: order.transactionProducts.map((product: ProductOrder) => product),\n },\n };\n // Backwards compatible event\n pleistyPush(\n 'checkout_finalized',\n {\n currency: \"RON\",\n items: ecommerce.purchase.products\n });\n\n // Backwards compatible event\n // TODO: Do we need the following 2 events ?\n pleistyPush('pageLoaded', {\n ecommerce,\n });\n\n pleistyPush('orderPlaced', {\n ...order,\n ecommerce,\n });\n\n return\n }\n default: {\n return\n }\n }\n}\n\nfunction getPurchaseObjectData(order: Order) {\n return {\n affiliation: order.transactionAffiliation,\n coupon: order.coupon ? order.coupon : null,\n id: order.orderGroup,\n revenue: order.transactionTotal,\n shipping: order.transactionShipping,\n tax: order.transactionTax,\n }\n}\n\nif (canUseDOM) {\n window.addEventListener('message', handleEvents)\n}\n\n```"
}
] |
code_pleisty-integration_db8ac71e
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/HomePageAccessoriesRecommendations.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { HP_ACCESSORIES_RECOMMENDATIONS_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\nconst HomePageAccessoriesRecommendations = () => <PleistyWrapper widgetId={HP_ACCESSORIES_RECOMMENDATIONS_PRODUCTS_WIDGET_ID}/>\n\nexport default HomePageAccessoriesRecommendations;\n\n```"
}
] |
code_pleisty-integration_8dfead15
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/ProductPageOtherRecommendations.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { PP_OTHER_RECOMMENDATIONS_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\nconst ProductPageOtherRecommendations = () => {\n return <PleistyWrapper widgetId={PP_OTHER_RECOMMENDATIONS_PRODUCTS_WIDGET_ID}/>\n}\nexport default ProductPageOtherRecommendations;\n\n```"
}
] |
code_pleisty-integration_5d16373e
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/HomePageSpecialForYou.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { HP_SPECIAL_FOR_YOU_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\n\nconst HomePageRecentlyViewedProducts = () => {\n return <PleistyWrapper widgetId={HP_SPECIAL_FOR_YOU_PRODUCTS_WIDGET_ID}/>\n}\nexport default HomePageRecentlyViewedProducts;\n\n```"
}
] |
code_pleisty-integration_a20a02af
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/SpecialForYou.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { SPECIAL_FOR_YOU_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\nconst SpecialForYou = () => {\n return <PleistyWrapper widgetId={SPECIAL_FOR_YOU_PRODUCTS_WIDGET_ID}/>\n}\n\nexport default SpecialForYou;\n\n```"
}
] |
code_pleisty-integration_a32b9e47
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/ProductPageSimilarProducts.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { PP_SIMILAR_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\n\nconst ProductPageRecentlyViewedProducts = () => {\n return <PleistyWrapper widgetId={PP_SIMILAR_PRODUCTS_WIDGET_ID}/>\n}\nexport default ProductPageRecentlyViewedProducts;\n\n```"
}
] |
code_pleisty-integration_67ee1c06
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/PleistyCarouselHistoryTest.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { PLEISTY_HISTORY_TEST_WIDGET_ID } from \"./utils/constants\";\n\nconst PleistyCarouselHistoryTest = () => {\n return <PleistyWrapper widgetId={PLEISTY_HISTORY_TEST_WIDGET_ID}/>\n}\nexport default PleistyCarouselHistoryTest;\n\n```"
}
] |
code_pleisty-integration_90a3cee2
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/package.json from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"scripts\": {\n \"test\": \"vtex-test-tools test\"\n },\n \"dependencies\": {\n \"react\": \"^16.13.1\",\n \"react-dom\": \"^16.13.1\",\n \"classnames\": \"^2.2.6\"\n },\n \"devDependencies\": {\n \"@apollo/react-testing\": \"^3.1.3\",\n \"@types/graphql\": \"^14.5.0\",\n \"@types/jest\": \"^25.1.5\",\n \"@types/node\": \"^13.11.0\",\n \"@types/react\": \"^16.9.31\",\n \"@types/react-intl\": \"^3.0.0\",\n \"@vtex/test-tools\": \"^3.1.0\",\n \"apollo-cache-inmemory\": \"^1.6.5\",\n \"apollo-client\": \"^2.6.8\",\n \"graphql\": \"^14.5.4\",\n \"react-intl\": \"^3.11.0\",\n \"typescript\": \"3.9.7\"\n }\n}\n\n```"
}
] |
code_pleisty-integration_a8b9fd8a
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/PleistyCarouselTest.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { PLEISTY_TEST_WIDGET_ID } from \"./utils/constants\";\n\nconst PleistyCarouselTest = () => {\n return <PleistyWrapper widgetId={PLEISTY_TEST_WIDGET_ID}/>\n}\nexport default PleistyCarouselTest;\n\n```"
}
] |
code_pleisty-integration_d5b86dc9
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/HomePageRecentlyViewedProducts.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { HP_RECENTLY_VIEWED_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\n\nconst HomePageRecentlyViewedProducts = () => {\n return <PleistyWrapper widgetId={HP_RECENTLY_VIEWED_PRODUCTS_WIDGET_ID}/>\n}\nexport default HomePageRecentlyViewedProducts;\n\n```"
}
] |
code_pleisty-integration_51dd26f5
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/HomePageRecommendationsForYou.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { HP_RECOMMENDATIONS_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\n\nconst HomePageRecommendationsForYou = () => {\n return <PleistyWrapper widgetId={HP_RECOMMENDATIONS_PRODUCTS_WIDGET_ID}/>\n}\n\nexport default HomePageRecommendationsForYou;\n\n```"
}
] |
code_pleisty-integration_3e2d595b
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/SimilarProducts.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport { PP_SIMILAR_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\n\n\nconst SimilarProducts = () => {\n return <PleistyWrapper widgetId={PP_SIMILAR_PRODUCTS_WIDGET_ID}/>\n}\nexport default SimilarProducts;\n\n```"
}
] |
code_pleisty-integration_d4ba45cc
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/RecentlyViewedProducts.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyWrapper from \"./Components/PleistyWrapper\";\nimport { RECENTLY_VIEWED_PRODUCTS_WIDGET_ID } from \"./utils/constants\";\n\n\nconst RecentlyViewedProducts = () => {\n return <PleistyWrapper widgetId={RECENTLY_VIEWED_PRODUCTS_WIDGET_ID}/>\n}\nexport default RecentlyViewedProducts;\n\n```"
}
] |
code_pleisty-integration_d29fe726
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/store/interfaces.json from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```json\n{\n \"special-for-you\": {\n \"component\": \"SpecialForYou\"\n },\n \"hp-special-for-you\": {\n \"component\": \"HomePageSpecialForYou\"\n },\n \"hp-accessories-recommendations\": {\n \"component\": \"HomePageAccessoriesRecommendations\"\n },\n \"recommendations-for-you\": {\n \"component\": \"HomePageRecommendationsForYou\"\n },\n \"recently-viewed-products\": {\n \"component\": \"RecentlyViewedProducts\"\n },\n \"hp-recently-viewed-products\": {\n \"component\": \"HomePageRecentlyViewedProducts\"\n },\n \"similar-products\": {\n \"component\": \"SimilarProducts\"\n },\n \"pp-similar-products\": {\n \"component\": \"ProductPageSimilarProducts\"\n },\n \"other-recommendations\": {\n \"component\": \"ProductPageOtherRecommendations\"\n },\n \"pleisty-carousel-test\": {\n \"component\": \"PleistyCarouselTest\"\n },\n \"pleisty-carousel-history-test\": {\n \"component\": \"PleistyCarouselHistoryTest\"\n },\n \"pixel.thank-you\": {\n \"component\": \"index\"\n }\n}\n\n```"
}
] |
code_pleisty-integration_f38db1ac
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/typings/events.d.ts from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport interface PixelMessage extends MessageEvent {\n data:\n | ProductViewData\n | ProductClickData\n | OrderPlacedData\n | OrderPlacedTrackedData\n | PageViewData\n | ProductImpressionData\n | AddToCartData\n | RemoveToCartData\n | CartChangedData\n | HomePageInfo\n | ProductPageInfoData\n | SearchPageInfoData\n | UserData\n | CartIdData\n | CartData\n}\n\nexport interface EventData {\n event: string\n eventName: string\n currency: string\n}\n\nexport interface PageInfoData extends EventData {\n event: 'pageInfo'\n eventName: 'vtex:pageInfo'\n accountName: string\n pageTitle: string\n pageUrl: string\n}\n\nexport interface UserData extends PageInfoData {\n eventType: 'userData'\n eventName: 'vtex:userData'\n firstName?: string\n lastName?: string\n document?: string\n id?: string\n email?: string\n phone?: string\n isAuthenticated: boolean\n}\n\nexport interface CartIdData extends PageInfoData {\n eventType: 'cartId'\n eventName: 'vtex:cartId'\n cartId: string\n}\n\nexport interface HomePageInfo extends PageInfoData {\n eventType: 'homeView'\n}\n\nexport interface ProductPageInfoData extends PageInfoData {\n eventType: 'productPageInfo'\n}\n\nexport interface SearchPageInfoData extends PageInfoData {\n eventType:\n | 'internalSiteSearchView'\n | 'categoryView'\n | 'departmentView'\n | 'emptySearchView'\n category?: CategoryMetaData\n department?: DepartmentMetaData\n search?: SearchMetaData\n}\n\ninterface CategoryMetaData {\n id: string\n name: string\n}\n\ninterface DepartmentMetaData {\n id: string\n name: string\n}\n\ninterface SearchMetaData {\n term: string\n category: CategoryMetaData\n results: number\n}\n\nexport interface PageViewData extends EventData {\n event: 'pageView'\n eventName: 'vtex:pageView'\n pageTitle: string\n pageUrl: string\n referrer: string\n}\n\nexport interface AddToCartData extends EventData {\n event: 'addToCart'\n eventName: 'vtex:addToCart'\n items: CartItem[]\n}\n\nexport interface RemoveToCartData extends EventData {\n event: 'removeFromCart'\n eventName: 'vtex:removeFromCart'\n items: CartItem[]\n}\n\nexport interface CartChangedData extends EventData {\n event: 'cartChanged'\n eventName: 'vtex:cartChanged'\n items: CartItem[]\n}\n\nexport interface OrderPlacedData extends Order, EventData {\n event: 'orderPlaced'\n eventName: 'vtex:orderPlaced'\n}\n\nexport interface OrderPlacedTrackedData extends Order, EventData {\n event: 'orderPlacedTracked'\n eventName: 'vtex:orderPlacedTracked'\n}\n\nexport interface ProductViewData extends EventData {\n event: 'productView'\n eventName: 'vtex:productView'\n product: Product\n}\n\nexport interface ProductClickData extends EventData {\n event: 'productClick'\n eventName: 'vtex:productClick'\n product: ProductSummary\n}\n\nexport interface ProductImpressionData extends EventData {\n event: 'productImpression'\n eventName: 'vtex:productImpression'\n impressions: Impression[]\n product?: ProductSummary // deprecated, use impressions list!\n position?: number // deprecated, use impressions list!\n list: string\n}\n\nexport interface CartLoadedData extends EventData {\n event: 'cartLoaded'\n eventName: 'vtex:cartLoaded'\n orderForm: OrderForm\n}\n\ninterface CartItemAdditionalInfo {\n brandName: string\n brandId: string\n}\n\ninterface CartItem {\n id: string\n productCategories: Record<string, string> | null\n additionalInfo: CartItemAdditionalInfo | null\n brand: string\n ean: string\n category: string\n detailUrl: string\n imageUrl: string\n name: string\n skuName: string\n price: number\n sellingPrice: number\n productId: string\n productRefId: string\n quantity: number\n skuId: string\n variant: string\n}\n\ninterface Totalizer {\n id: string\n name: string\n value: number\n}\n\ninterface Seller {\n id: string\n name: string\n logo: string\n}\n\ninterface ClientProfileData {\n email: string\n firstName: string\n lastName: string\n}\n\ninterface Address {\n addressId: string\n postalCode: string\n street: string\n number: string\n neighborhood: string\n complement: string\n city: string\n state: string\n}\n\ninterface DeliveryOption {\n id: string\n price: number\n estimate: string\n isSelected: boolean\n}\n\ninterface Shipping {\n selectedAddress: Address\n deliveryOptions?: DeliveryOption[]\n}\n\ninterface MarketingData {\n coupon: string\n utmCampaign: string\n utmSource: string\n utmMedium: string\n utmiCampaign: string\n utmiPage: string\n utmiPart: string\n}\n\nexport interface OrderForm {\n id: string\n totalizers: Totalizer[]\n sellers: Seller[]\n salesChannel: string\n items: CartItem[]\n canEditData: boolean\n loggedIn: boolean\n clientProfileData?: ClientProfileData\n shipping?: Shipping\n value: number\n marketingData?: MarketingData\n}\n\nexport interface Order {\n accountName: string\n corporateName: string\n coupon: string\n currency: string\n openTextField: string\n orderGroup: string\n salesChannel: string\n visitorAddressCity: string\n visitorAddressComplement: string\n visitorAddressCountry: string\n visitorAddressNeighborhood: string\n visitorAddressNumber: string\n visitorAddressPostalCode: string\n visitorAddressState: string\n visitorAddressStreet: string\n visitorContactInfo: string[]\n visitorContactPhone: string\n visitorType: string\n transactionId: string\n transactionDate: string\n transactionAffiliation: string\n transactionTotal: number\n transactionShipping: number\n transactionSubtotal: number\n transactionDiscounts: number\n transactionTax: number\n transactionCurrency: string\n transactionPaymentType: PaymentType[]\n transactionShippingMethod: ShippingMethod[]\n transactionLatestShippingEstimate: Date\n transactionProducts: ProductOrder[]\n transactionPayment: {\n id: string\n }\n}\n\nexport interface Impression {\n product: ProductSummary\n position: number\n}\n\nexport interface PaymentType {\n group: string\n paymentSystemName: string\n installments: number\n value: number\n}\n\nexport interface ShippingMethod {\n itemId: string\n selectedSla: string\n}\n\nexport interface ProductOrder {\n id: string\n name: string\n sku: string\n skuRefId: string\n skuName: string\n productRefId: string\n ean: string\n slug: string\n brand: string\n brandId: string\n seller: string\n sellerId: string\n category: string\n categoryId: string\n categoryTree: string[]\n categoryIdTree: string[]\n priceTags: PriceTag[]\n originalPrice: number\n price: number\n sellingPrice: number\n tax: number\n quantity: number\n // eslint-disable-next-line @typescript-eslint/no-explicit-any\n components: any[]\n measurementUnit: string\n unitMultiplier: number\n}\n\nexport interface PriceTag {\n identifier: string\n isPercentual: boolean\n value: number\n}\n\nexport interface Product {\n brand: string\n brandId: string\n categories: string[]\n categoryId: string\n categoryTree: Array<{ id: string; name: string }>\n detailUrl: string\n items: Item[]\n linkText: string\n productId: string\n productName: string\n productReference: string\n selectedSku: Item\n}\n\nexport interface Item {\n itemId: string\n name: string\n ean: string\n referenceId: { Key: string; Value: string }\n imageUrl: string\n sellers: Seller[]\n}\n\nexport interface ProductSummary {\n brand: string\n brandId: string\n categories: string[]\n items: ItemSummary[]\n linkText: string\n productId: string\n productName: string\n productReference: string\n sku: ItemSummary\n}\n\ninterface ItemSummary {\n itemId: string\n ean: string\n name: string\n referenceId: { Key: string; Value: string }\n seller: Seller\n sellers: Seller[]\n}\n\nexport interface Seller {\n commertialOffer: CommertialOffer\n sellerId: string\n}\n\nexport interface CommertialOffer {\n Price: number\n ListPrice: number\n AvailableQuantity: number\n}\n\n```"
}
] |
code_pleisty-integration_07640581
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/typings/vtex.render-runtime.d.ts from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\n/* Typings for `render-runtime` */\ndeclare module 'vtex.render-runtime' {\n import { Component, ComponentType, ReactElement, ReactType } from 'react'\n\n export interface NavigationOptions {\n page: string\n params?: any\n }\n\n export interface RenderContextProps {\n runtime: {\n navigate: (options: NavigationOptions) => void\n }\n }\n\n interface ExtensionPointProps {\n id: string\n [key: string]: any\n }\n\n export const ExtensionPoint: ComponentType<ExtensionPointProps>\n\n interface ChildBlockProps {\n id: string\n }\n\n export const ChildBlock: ComponentType<ChildBlockProps>\n export const useChildBlock = function({\n id: string,\n }): Record<string, unknown> {}\n\n export const Helmet: ReactElement\n export const Link: ReactType\n export const NoSSR: ReactElement\n export const RenderContextConsumer: ReactElement\n export const canUseDOM: boolean\n export const withRuntimeContext: <TOriginalProps extends unknown>(\n Component: ComponentType<TOriginalProps & RenderContextProps>\n ) => ComponentType<TOriginalProps>\n}\n\n```"
}
] |
code_pleisty-integration_71d83bf4
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/typings/global.d.ts from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\ninterface IPleistyProductProps {\n product: IPleistyProduct;\n}\n\ninterface IPleistyProduct {\n item_stock: string;\n item_cat3: string;\n item_pricenum: string;\n item_id: string;\n item_oldpricestring: string;\n item_discount: string;\n item_cat2: string;\n item_isnew: string;\n item_formatsenzor: string;\n item_pricestring: string;\n item_sku: string;\n item_cat1: string;\n item_imgorig: string;\n item_aparatmonturaobiectiv: string;\n item_oldpricenum: string;\n item_isonsale: string;\n item_brand: string;\n item_title: string;\n item_img: string;\n is_history?: string;\n is_hidden?: string;\n is_selected?: string;\n _item_url: string;\n _ih: string;\n}\n\ninterface IPleistyGlobalResponse {\n WIDGET_PARAMS?: string;\n curr_item_price_and_class: string;\n host_part: string;\n item_to_rdr: any[];\n request_url: string;\n special_rule: any;\n title: string;\n rec_items: IPleistyProduct[];\n}\n\ninterface IPleistyWrapperProps {\n widgetId: string;\n}\n\ninterface IPleistyCarouselProps {\n pleistyProducts: IPleistyProduct[];\n widgetParam?: string;\n}\n\ninterface IPleistyHistoryNavigationProps {\n pleistyHistoryProducts: IPleistyProduct[];\n handleClickHistoryNavigation: (any) => void;\n children?: JSX.Element;\n}\n\ninterface Window extends Window {\n dataLayer: any[];\n}\n \n```"
}
] |
code_pleisty-integration_e95faa3b
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/utils/pleisty-utils.ts from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport const pushPleistyWidgetId = (widgetId: string, callBackFn: (errors, productsResponse) => void) => {\n // @ts-ignore\n const pleistyGlobal = window._pleistyq;\n if (pleistyGlobal) {\n pleistyGlobal.push(['_req_widget_callback', widgetId,\n {\n \"_items_cnt\": 20,\n \"_params\": []\n }, callBackFn]);\n }\n};\n\nexport const pleistyPush = (event: any, objectToPush: any) => {\n // @ts-ignore\n const globalPleisty = window._pleistyq;\n\n if (globalPleisty) {\n globalPleisty.push([event, objectToPush])\n }\n};\n\n```"
}
] |
code_pleisty-integration_aa77570d
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/utils/constants.ts from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```typescript\nexport const HP_RECOMMENDATIONS_PRODUCTS_WIDGET_ID = \"W_af7d6744aa292e1a3a29364a7bdf45f7\";\nexport const HP_RECENTLY_VIEWED_PRODUCTS_WIDGET_ID = \"W_bc8af84645a4bab700077595f5e9e0ae\";\nexport const HP_SPECIAL_FOR_YOU_PRODUCTS_WIDGET_ID = \"W_04bd9f7452804c6916686d64a48286b0\";\nexport const HP_ACCESSORIES_RECOMMENDATIONS_PRODUCTS_WIDGET_ID = \"W_38a77bd7472e93329499a72634e83ce9\";\nexport const RECENTLY_VIEWED_PRODUCTS_WIDGET_ID = \"W_bc8af84645a4bab700077595f5e9e0ae-wrapper\";\nexport const PP_SIMILAR_PRODUCTS_WIDGET_ID = \"W_eb764552ba03762938dc46db33a51ce2\";\nexport const PP_OTHER_RECOMMENDATIONS_PRODUCTS_WIDGET_ID = \"W_bbe0d8d76440453220f7910e8160ae76\";\nexport const SPECIAL_FOR_YOU_PRODUCTS_WIDGET_ID = \"W_5aaba4613bb64f2f64becdc818a679ac\";\nexport const PLEISTY_TEST_WIDGET_ID = \"W_9cdd23ebded8f5cca0c08796669b29b9\";\nexport const PLEISTY_HISTORY_TEST_WIDGET_ID = \"W_0cdc2f51f1677778efbdaf55de1d0814\";\n\n\nexport const ITEMS_PER_PAGE = {\n desktop: 5,\n tablet: 3,\n phone: 2\n}\nexport const INFINITE = true;\nexport const NAVIGATION_STEP = \"page\";\nexport const SHOW_NAVIGATION_ARROWS = \"desktopOnly\";\nexport const SHOW_PAGINATION_DOTS = \"always\";\nexport const USE_PAGINATION = true;\nexport const FULL_WIDTH = false;\nexport const ARROW_SIZE = 25;\n\n\n```"
}
] |
code_pleisty-integration_c4808c92
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/Components/PleistyCarousel.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React from 'react';\nimport PleistyProduct from \"./PleistyProduct\";\n// @ts-ignore\nimport { SliderLayout } from 'vtex.slider-layout';\nimport {\n ARROW_SIZE,\n FULL_WIDTH,\n INFINITE,\n ITEMS_PER_PAGE,\n NAVIGATION_STEP,\n SHOW_NAVIGATION_ARROWS,\n SHOW_PAGINATION_DOTS,\n USE_PAGINATION\n} from \"../utils/constants\";\n\n\nconst PleistyCarousel = (props: IPleistyCarouselProps) => {\n\n const { pleistyProducts } = props;\n return (\n <SliderLayout\n key={props.widgetParam}\n totalItems={pleistyProducts?.length}\n infinite={INFINITE}\n itemsPerPage={ITEMS_PER_PAGE}\n navigationStep={NAVIGATION_STEP}\n showNavigationArrows={SHOW_NAVIGATION_ARROWS}\n showPaginationDots={SHOW_PAGINATION_DOTS}\n usePagination={USE_PAGINATION}\n fullWidth={FULL_WIDTH}\n arrowSize={ARROW_SIZE}\n >\n {pleistyProducts.map((pleistyProduct: IPleistyProduct) => (\n <React.Fragment key={pleistyProduct.item_sku}>\n <PleistyProduct key={pleistyProduct.item_sku} product={pleistyProduct}/>\n </React.Fragment>\n ))}\n </SliderLayout>\n )\n}\nexport default PleistyCarousel;\n\n```"
}
] |
code_pleisty-integration_265ee906
|
[
{
"role": "system",
"content": "You are an expert VTEX IO developer. You specialize in building VTEX Store Framework apps, React components, GraphQL APIs, and Node.js services for e-commerce platforms."
},
{
"role": "user",
"content": "Show me the implementation of pleisty-integration/react/Components/PleistyWrapper.tsx from the pleisty-integration VTEX app."
},
{
"role": "assistant",
"content": "Here's the implementation:\n\n```tsx\nimport React, { useCallback, useEffect, useState } from 'react';\nimport { pushPleistyWidgetId } from \"../utils/pleisty-utils\";\nimport PleistyCarousel from \"./PleistyCarousel\";\nimport PleistyHistoryNavigation from \"./PleistyHistoryNavigation\";\n// @ts-ignore\nimport { useCssHandles } from 'vtex.css-handles'\n\nconst CSS_HANDLES = [\n 'pleisty-shelf-title',\n 'pleisty-title'\n] as const;\n\nconst PleistyWrapper = (props: IPleistyWrapperProps) => {\n const [pleistyProducts, setPleistyProducts] = useState<IPleistyProduct[]>([]);\n const [pleistyHistoryProducts, setPleistyHistoryProducts] = useState<IPleistyProduct[]>([]);\n const [pleistyGlobal, setPleistyGlobal] = useState<IPleistyGlobalResponse>();\n const isTypeHistory = !!pleistyHistoryProducts.length;\n const handles = useCssHandles(CSS_HANDLES);\n\n useEffect(() => {\n if (!pleistyProducts.length) {\n handleSetPleistyProductsByWidgetId(props.widgetId);\n }\n }, []);\n\n const handleClickHistoryNavigation = useCallback((selectedPleistyProduct: IPleistyProduct) => {\n handleSetPleistyProductsByWidgetId(`${props.widgetId}.${selectedPleistyProduct._ih}`);\n }, [props.widgetId]);\n\n const handleSetPleistyProductsByWidgetId = useCallback((widgetId: string) => {\n pushPleistyWidgetId(widgetId, (errors, response) => {\n if (errors) {\n console.error(errors);\n }\n if (response) {\n const items: IPleistyProduct[] = response.items?.filter((pleistyProduct: IPleistyProduct) => !pleistyProduct.is_history || pleistyProduct.is_selected === \"true\");\n const global: IPleistyGlobalResponse = response.global;\n setPleistyProducts(items);\n setPleistyGlobal(global);\n const historyProducts = response.items?.filter((pleistyProduct: IPleistyProduct) => pleistyProduct.is_history);\n setPleistyHistoryProducts(historyProducts);\n }\n });\n }, [pleistyProducts]);\n\n return pleistyProducts.length ? (\n <React.Fragment>\n <div className={handles[\"pleisty-shelf-title\"]}>\n <h5 className={handles[\"pleisty-title\"]}>{isTypeHistory ? \"Produse recent vizualizate si recomandari\" : pleistyGlobal?.title}</h5>\n </div>\n {isTypeHistory ? (\n <PleistyHistoryNavigation\n pleistyHistoryProducts={pleistyHistoryProducts}\n handleClickHistoryNavigation={handleClickHistoryNavigation}\n >\n <PleistyCarousel widgetParam={pleistyGlobal?.WIDGET_PARAMS} pleistyProducts={pleistyProducts}/>\n </PleistyHistoryNavigation>\n ) : (\n <PleistyCarousel widgetParam={pleistyGlobal?.WIDGET_PARAMS} pleistyProducts={pleistyProducts}/>\n )}\n </React.Fragment>\n ) : null;\n}\nexport default PleistyWrapper;\n\n```"
}
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.