The back-end will not accept query parameters that it does not recognize. This is to help API users discover typos in their requests. Some related discussion on this.
I think the queryScope state should be stored somewhere else.
Or alternatively (perhaps even better), when performing the scoped search action, the user should be navigated to the /search route, and there a query param would be fitting. This also fixes a UX issue, namely that now pressing the search moves focus down, which is kind of hard to spot since the user is looking at the top right.
Invalid query param: queryscopeThe back-end will not accept query parameters that it does not recognize. This is to help API users discover typos in their requests. Some related discussion on this.
I think the
queryScopestate should be stored somewhere else.Or alternatively (perhaps even better), when performing the scoped search action, the user should be navigated to the
/searchroute, and there a query param would be fitting. This also fixes a UX issue, namely that now pressing the search moves focus down, which is kind of hard to spot since the user is looking at the top right.