vtex-apps/store-theme

VTEX Store Theme

store-theme's Issues

A malfunctioning link occurs when a user clicks on the HTML `<a>` tag in the README file.

Describe the bug
A malfunctioning link occurs when a user clicks on the HTML <a> tag in the README file.

To Reproduce
Steps to reproduce the behavior:

1. Go to the readme https://github.com/vtex-apps/store-theme#readme
2. Click on hyberlinks(html <a) Build a store using VTEX IO or Store
3. see 404 error after redirection

Expected behavior
both hyberlink able to redirect with correct contents where

• Build a store using VTEX IO expect to redirect to article that guide how to build-stores-with-store-framework
• Store expect to redirect to https://github.com/vtex-apps/store#readme

Screenshots of Actual behaviours
Redirection issue due to hyberlink Build a store using VTEX IO

Redirection issue due to hyberlink Store

Não funciona

Olá, estou tentando correr esse projeto e nunca funciona, clono o projeto, corro com vtex link e tento acessar as rotas que mostra no console e não mostra nada. Tento usar a rota default e tomo o erro na imagem:
PS: A unica branch que funciona é a account/pages

Crear un componente que sea editable

Hola! Estoy intentando crear un componente con un comportamiento peculiar, quiero que este componente permita cargar otros componentes, algo como un gestor de componentes. algo simple y que ya me funciono. pero cuando importo cada uno de los componentes encuentro que estos no son editables

He echo el análisis del proceso para poder editar un componente en el StoreFront y llegue al proyecto (https://github.com/vtex-apps/render-runtime) donde se encuentra toda esta lógica que permite editar un componente, mi pregunta es. como puedo yo replicar este proceso para que los componentes que se carguen sean editables como cuando son cargados por medio del ExtensionPoint en el pages.json del dreamstore.

Error when linking `couldn't find a block "product-separator"`

Describe the bug
When starting a brand new repo with the latest version of this app (3.5.0), linking gives an error because the blocks configuration has a block that does not exist.
App build failed with message: Error resolving block "flex-layout.col#product-price": I couldn't find a block "product-separator". You need to declare it or depend on an app that declares it.

To Reproduce
Steps to reproduce the behavior:

1. Just link this app on the latest version

Desktop (please complete the following information):

• OS: macOS Mojave
• Browser Chrome
• Version latest

Store.home interface not rendering components

Describe the bug
I've tried to add a store.home block but it seems like the component is not rendering no matter what. There's no error when building or linking, also I've tried with some couple of other components (from blank to complex components) but It doesn't seems to be a problem related to the component itself as there's no difference when I try with another. Note: If I do the same steps by adding my component to appear as a store.product block it actually works.

To Reproduce
Steps to reproduce the behavior:
Clone vtex.store repo
Add a component as allowed in the store interface
Add it in your store.home store-theme app

Expected behavior
When a component is allowed in the store interface, it should be allowed in every extension/descendants of store (i.e: store.home, store.product).

Desktop (please complete the following information):

• OS: macOS
• Browser: chrome

Error: pages-graphql

I was following vtex.io getting start documentation, but seens that "vtex init" only brings a clean theme, so i downloaded store-theme and tryed to link :

Error: pages-graphql

Vtex link fails with a clean install of store-theme

Describe the bug
When I clone store-theme and run vtex link (with workspace already defined), the console throws an error due reviews-and-ratings.

To Reproduce
Steps to reproduce the behavior:

1. Clone vtex-apps/store-theme
2. Checkout branch "master"
3. Run vtex link command
4. See error

Expected behavior
The link should be established without any errors.

Screenshots
vtex link output

Desktop (please complete the following information):

• OS: PopOS! 20.04
• Browser: -
• CLI VERSION: vtex/3.0.0 linux-x64 node-v16.13.1

Additional context
When we remove vtex.reviews-and-ratings": "3.x" from peerDependencies at manifest.json, it works.

Layout not same store-theme default

Describe the bug
When run vtex browse after vtex link, this layout is same from legacy

To Reproduce
Steps to reproduce the behavior:

1. Clone repository
2. Change data on manifest.json
3. Run vtex link

Expected behavior
Default store-theme layout

Desktop (please complete the following information):

• OS: macOS Big Sur
• Browser Chrome

Additional context
Followed steps by this video: https://www.youtube.com/watch?v=4hHDbIXAcKc