Allow Commerce Search v3 for Local Development
Local debugging for Commerce Search v3 is currently unavailable, and renders the site completely unusable. This is, to put it bluntly, absolutely unacceptable. As far as I can tell, the only workaround presently is to switch to Search v2 for local development. At very least, there should be a way to have the system default to Search v2 when working locally, regardless of what is configured.
Kiran Ramaswamy
shared this idea
I can confirm that currently Commerce Search v3 does not support Local Development.
- Until local support is available, partners are currently working from Sandbox environments or if working on non search related activities they may be switching to alternative provider while working locally.
While the suggestion to automatically fallback to Search v2 during local development is technically possible, it would mask actual system behavior and could lead to incorrect assumptions, missed issues, or inconsistent environment (sandbox vs local). For that reason, we are unlikely going to implement an automatic fallback to alternative search provider and switching search providers will remain a manual action at this time.
- We fully understand your frustration, and how the inability to debug or run the site locally with Search v3 enabled is a significant disruption.
- We are actively evaluating options to enable limited local development against sandbox instances, and work is underway to determine what is feasible and the associated timing.
Please continue to share related impact and feedback and we will be sure to bring that to our teams as they review this request.
