[Experimental] Refresh product collections that don't support the interactivity API

[samueljseay]

Changes proposed in this Pull Request:

The new interactivity API filter blocks don't refresh the page when updating a filter (in most cases) because the new product collection can handle that.

But we need to still support classic template and the soon to be deprecated "Products (Beta)" block. In this PR we add a flag to client side data for those cases, we use that flag to determine if a full page refresh is needed. Bottom line: if at least one of these is present on a page we will do full page refresh when updating the filters. This will be easy to change later as we do all the navigation for interactivity filters from a single function.

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

1. In site editor -> templates, edit the template block, add the new interactivity filters and the classic template block. To avoid confusion also remove "product collection" from shop page if it happens to be there already.
2. Load the shop page and change some of the filters, for each a refresh of the page should happen and the respective product collection should be properly filtered.
3. Create a page or template with the interactivity filters nested inside "Products (Beta)". There will be warning not to do this for each block, but thats ok.
4. Preview your new template or page and same as 2, change some filters and see a page refresh and see the filters applied.
5. You can also test the current case in a template or page add "Product Collection (Beta)" with new interactivity filters nested (and ensure no classic or product beta block is on the page). Preview the new content and apply the filters. the page should not refresh but filters should still be applied.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

[Experimental] Add a flag that will force page refresh when combining interactivity filters with classic template or products (beta) blocks.

Comment

[github-actions]

Hi @dinhtungdu,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[github-actions]

Test Results Summary

Commit SHA: acd6a55

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	0m 37s
E2E Tests	308	0	0	17	0	325	7m 16s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[dinhtungdu]

The PR is testing great for me. I only have some comments on the testing instructions:

• This PR doesn't have the Experimental prefix, the QA team will pick it up for testing. We should state that this can't be tested without Introduce the new front-end filter blocks in beta state #44489.
• In the testing instructions you mentioned:

Create a page or template with the interactivity filters nested inside "Products (Beta)". There will be warning not to do this for each block, but thats ok.

I think we should also mention here that even new filter blocks work inside Products (Beta), we don't have a plan to remove the warning when used with Products (Beta) block or update the copy (which mentions the Product Collection only) because the former is being deprecated soon.

Approving because this is working and testing as expected.

[samueljseay]

This PR doesn't have the Experimental prefix, the QA team will pick it up for testing. We should state that this can't be tested without #44489.

@dinhtungdu yes true, 🤔 should we maybe just add [Experimental] prefix here? Then we could do general testing of this when we merge #44489 ?

I think we should also mention here that even new filter blocks work inside Products (Beta), we don't have a plan to remove the warning when used with Products (Beta) block or update the copy (which mentions the Product Collection only) because the former is being deprecated soon.

When you say mention, you just want to add this detail in the PR description? Maybe its not too important if we mark this experimental, but of course happy to add more explanation.

[dinhtungdu]

should we maybe just add [Experimental] prefix here? Then we could do general testing of this when we merge #44489 ?

@samueljseay Yeah, sounds good to me.

When you say mention, you just want to add this detail in the PR description? Maybe its not too important if we mark this experimental, but of course happy to add more explanation.

Yes, I mean the description of the PR. But if we mark this one as experimental, then I agree that it's not necessary.