Tweakwise App & API

• We've made it possible to get categories in autocomplete results even if the filter template with categories is hidden
• The backend API’s / attribute endpoint’s documentation was unclear about which sources could be filtered. Besides, the names of the sources were in Dutch. We’ve changed the names to English and added documentation to clarify which sources can be filtered.
• It was possible for customers to import categories with negative IDs. This was something that should not have been possible in the first place, and in some instances, it broke applications in various places. With a new validation rule, it is no longer possible to import categories with negative IDs anymore.
• New feature: we have implemented a property component for Personal Merchandising. This component allows setting up a configuration for the product, which can be used in Personal Merchandising based on the attribute AND its value.
• From now on, we show an error message in the derived attributes module when a query eventually cannot be processed by SQL. 
• We added a validation rule during feed import that prevents category trees with circular dependencies from being imported. A simple example is when category B has category A as its parent, but category A also has category B as its parent, causing an infinitely nested category structure because they reference each other.
• Another validation rule when importing a feed was added. Customers now aren’t able to import categories anymore for which no name is specified.
• New feature: a long desired request, but finally, we have made it possible to show recommendations through Javascript. This feature works standalone (even for non-JS customers) by simply adding a code snippet with a simple configuration on your website. For every recommendation set up in Tweakwise App, we’ve added some example code on how to implement it using our JS implementation. This can be found under the ‘info implementation’ tab. Custom styling is possible by writing (and hosting) your own CSS, as it is not yet possible to inherit previously customized styling. We expect this to be added soon as the default behavior.

Javascript implementations

• We've fixed a bug where the Javascript wouldn't show the selected filters correctly when customers would try to change the filters from outside of the JS implementation. 
• We have added plurality translations for only one search or navigation result. For example, instead of showing: "1 search results for "search term"." we now show "1 search result for "search term".". This change has been applied to all available languages.