[UPDATE 01/04/2020] 3.11.1: Fix #163
General
- Updated documentation
Search Parts
- [BREAKING CHANGE] Replaced the pagination Web Part by a web component. You can still decide where to put the component in the template + additional property pane options. PR #155. If you had custom templates and need pagination, refer to https://microsoft-search.github.io/pnp-modern-search/search-parts/search-pagination/.
- [BREAKING CHANGE]. Removed the search navigation Web Part. Replaced by the search verticals Web Part. PR #155
- Added an
instanceId
information in the Handlebars context for templates to be able to scope CSS styles per Web part instance. PR #155 - [BREAKING CHANGE] Removed the NLP feature from the Search Box. Even if you didn't use this feature, you will have to reconnect your search box with the Search Results WP. See https://microsoft-search.github.io/pnp-modern-search/search-parts/search-results/#search-settings.
- Added support for faster development with a separate webpack dev server. PR #144
- Added a per refiner option to be able to filter refinement values if too many displayed. PR #146
Fixes
- Fixed #118 Now search verticals fit nicely in responsive mode.
- Fixed #106 A
map
instead of afilter
was used to see if a current date range refiner was selected causing a reset of the refinement count and a null rendering. - Fixed #134 Added the logic to resolve tokens in the query template field for search verticals.
- Fixed #135 Added a default image when a 404 is returned.
- Fixed #132 Now the WP title is hidden as well when the "Show blank" option is set.
- Fixed #129 The 'Size' managed property was not returning the correct refinement name. Now, we use the refiner name every time regardless the value returned by the API.