update: improve search behavior guide#688
Open
julia-rabello wants to merge 2 commits into
Open
Conversation
Contributor
🧭 Navigation Generation Report❌ Validation Status: FAILEDParse errors: files could not be processed • Duplicate conflicts: 7 slug conflicts found 📝 Auto-commit: Navigation changes committed by workflow (commit d147d7d) 📊 Generation Details (click to expand)
🔗 Duplicate Slug Conflicts (7 conflicts)
📋 Generation Log: - Full log: Download navgen.log Generated by nav-generation workflow |
| Quando o cliente abre um link da loja no navegador, a busca por ID costuma montar o endereço no caminho (path), com `map=ft`. Nesse padrão não entram os parâmetros de string de consulta `query` ou `q`. | ||
|
|
||
| * **Um item:** `[endereço da loja]/[tipo do id]:[id_1]?map=ft` | ||
| * **Vários itens (mesmo tipo de ID):** `[endereço da loja]/[tipo do id]:[id_1];[id_2];[id_3]?map=ft` |
Contributor
There was a problem hiding this comment.
Senti falta de exemplos aqui. Não entendi o que é [tipo do id], por exemplo.
| Separe os valores com ponto e vírgula `;` e escreva o tipo da ID uma vez só, por exemplo: `?query=product:98765;98743` (equivale a `?query=product.id:98765;98743`) ou `?query=sku.id:100;200`. | ||
|
|
||
| Para buscar a partir da URL da sua loja, adicione parâmetros de busca (*query*) no final da URL da loja, respeitando uma das estruturas a seguir: | ||
| Os possíveis valores para o tipo de ID são `product.id`, `sku.id`, `sku.ean`, `sku.reference`, `product.link` ou `id` (ProductID, ProductRefID, SKUID, SKURefID e EAN). Todos os IDs de uma mesma busca devem ser do mesmo tipo. |
Contributor
There was a problem hiding this comment.
Isso vale também para storefront? Aqui parece que é só pra API.
| * **Um item:** `[endereço da loja]/[tipo do id]:[id_1]?map=ft` | ||
| * **Vários itens (mesmo tipo de ID):** `[endereço da loja]/[tipo do id]:[id_1];[id_2];[id_3]?map=ft` | ||
|
|
||
| ### Busca por ID na API do Intelligent Search |
Contributor
There was a problem hiding this comment.
Não conheço o público e casos de uso desse produto. Mas me ocorre que essa seção ficou um pouco técnica demais para o Help Center.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Provide a concise description of the change introduced by this PR.
Example: “Updates the Checkout overview to include new webhook behavior.”
Type of change
Checklist
AI review instructions
This repository supports automated AI reviews for Markdown files in the
docs/ptfolder.To run reviews on this PR, add at least one of the following labels:
AI style review: evaluates tone and adherence to VTEX style guidelines.AI grammar review: identifies grammar and spelling issues.Once at least one label is added, the review(s) will run automatically.
After the review is completed, the corresponding label will be removed and the label
AI reviewedwill be added to the PR.Note
To rerun a review, remove and add the desired label again.