An SRI check is available for this SDK. For more information, see the SDK Subresource Integrity page.
Results per pagein a website, they did not appear right and users needed to adjust the CSS to display them correctly. This is now fixed: We improved the default layout so that these components display as expected.
Refinement Tabscomponent. This is now fixed.
/apisrequest. It caused the SDK Client to sometimes lose the API URL under some specific configurations. This is now fixed.
connectionEntryPointparameter, you can use the entry point that suits you better.
applySplitQueryMaxCharactersin store property
advancedSearchOptions. This lets you set the max number of characters that a query should have to split.
searchParamsand updated the screenshots in the SDK builder page.
advancedSearchOptionsto properties in the "Searching with the store" section.
advancedSearchOptionsto properties in the "Reading the store state" section.
statscomponent with new options and samples images.
Autocompletercomponent now uses the width of the linked input automatically.
Semantic Autocompleterno longer disappeared after the user performed a query. This is now fixed.
Instantscomponent to improve its look.
unlinkFromInputin the following components:
Last Chance. Both methods provide a way to remove linked inputs from the components.
Autocompletercomponent. This option allows users to set the number of suggestions the autocompleter displays.
typein the SDK Builder. This new option allows users to select the type of UI that they want to built. The current available options are a standard UI, a UI with Semantic autocompleter, or a UI that uses the “Instant results” component instead of “Results”.
Searchboxcomponent now maintains the user query after the user sends the request. Previously, the query was removed after showing the results.
Resultscomponent usually displayed the Titles in capital letters. From now on, this is no longer the case.
Last chancecomponent was showing briefly when the query had no results, if the user had done a previous search that resulted in a
Last chanceearlier. This is now fixed.
Semantic autocompleteronly checked the last character of the text to apply or not the
debounceTime, depending on the trigger characters. This meant that if the user for some reason started writing text elsewhere than the end of the query, there was a possibility the debounce time was ignored.
Semantic autocompletercomponents so they behave like popovers. This makes it easier to implement these components in client pages without styling conflicts.
titleparameter in the following components: Results, instants, instant results and last chance. This parameter allows users to change the attribute used as a title. By default, the value of this parameter is "highlightedTitle".
maxResultsparameter to a minimum automatically if the search does not use filters, sorting, or pagination. This improves the performance speed of the system as it reduces the number of non-relevant content retrieved.
&), these characters were being matched by the autocompleter. This is now fixed and the Autocompleter now ignores the codification of special characters
SortBycomponent was not updating the results with the new sorting. This is now fixed and the results are now updated with the different sortings, as needed.
maxResultsparameter dynamically on the queries.
untilReadymethod from client, so it automatically resolves the promise.
autocompletercomponent: Enhance the
setInputElementmethod to also listen to new character inputs to updates the query.
last chancecomponent: When tracking "Contact submit" event, it will now log the user question.
autocompletecomponent click tracking