Skip to content

Commit 23226f7

Browse files
create known issue: [en] 1014701
1 parent 30478f4 commit 23226f7

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: 'Autocomplete Suggestion API removes special characters from the product name'
3+
slug: autocomplete-suggestion-api-removes-special-characters-from-the-product-name
4+
status: PUBLISHED
5+
createdAt: 2025-10-31T17:39:29.156Z
6+
updatedAt: 2025-10-31T17:39:29.156Z
7+
contentType: knownIssue
8+
productTeam: Intelligent Search
9+
author: 2mXZkbi0oi061KicTExNjo
10+
tag: Intelligent Search
11+
slugEN: autocomplete-suggestion-api-removes-special-characters-from-the-product-name
12+
locale: en
13+
kiStatus: Backlog
14+
internalReference: 1014701
15+
---
16+
17+
## Summary
18+
19+
20+
This issue occurs when searching for a term, and the autocomplete suggestion returns terms without special characters, even if the search term contains any special character, resulting in incorrect search results.
21+
22+
23+
#### Simulation
24+
25+
26+
27+
1. Request for the API route GET `https://..com.br/api/io/_v/api/intelligent-search/autocomplete_suggestions?query=` or use the search bar component to return suggestions for autocomplete for a giving search term(s).
28+
2. Observe the autocomplete suggestions provided by the system.
29+
3. Note that any special character is missing from the returned suggestions for autocomplete.
30+
31+
For example, if the term "headphone" is searched in the autocomplete suggestion API or search component, the suggestion results, if containing a special character in the name, will be displayed as "Headphone Bluetooth 5 0" instead of having the dot in the number "5.0". The correct format should be "Headphone Bluetooth 5.0". The same happens if a search already contains a special character, for example "headphone 5.0", it'll also return "Headphone Bluetooth 5 0".
32+
33+
When selecting this suggestion in the product_search API, will not return results.
34+
35+
36+
#### Workaround
37+
38+
39+
N/A
40+

0 commit comments

Comments
 (0)