Adding caching support to the SP search data source

[erkanch]

I frequently use the results web part to render dynamic content on the landing pages of intranets. For instance, I use the ViewsRecent to sort news or pages to display "trending" content or sort by last modified to display the recent content, etc. None of these queries use a dynamic search query or filter. So, it becomes redundant to invoke postquery every single time. This new cache timeout setting provides a mechanism to cache the search results for up to 240 minutes as long as the query or the filter or any other settings don't change. This would also help during heavy traffic to help minimize the risk of getting throttled.

[wobba]

Thank you @erkanch. Please add a doc update as part of your change so we document the new settings. You should also look at using the "PnP - Search Rollup" version which turns off dynamic data if you don't need it.

[erkanch]

Hi @wobba I've added the details to the documentation. Is the rollup web part in a separate project? I don't see it mentioned in https://microsoft-search.github.io/pnp-modern-search/#whats-included nor do I see a directory under src/webparts/

[sonarqubecloud]

Quality Gate failed

Failed conditions
25.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[wobba]

Hi @wobba I've added the details to the documentation. Is the rollup web part in a separate project? I don't see it mentioned in https://microsoft-search.github.io/pnp-modern-search/#whats-included nor do I see a directory under src/webparts/

It's a different version when you pick web part after install. It's the same, just a different manifest.