From 7ecbcd569ef9d90efa078001f03cf629ad972eb7 Mon Sep 17 00:00:00 2001 From: Olga Bulat Date: Wed, 6 Mar 2024 07:13:12 +0300 Subject: [PATCH] Update documentation/projects/proposals/additional_search_views/20230719-implementation_plan_additional_search_views.md Co-authored-by: zack <6351754+zackkrida@users.noreply.github.com> --- .../20230719-implementation_plan_additional_search_views.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/projects/proposals/additional_search_views/20230719-implementation_plan_additional_search_views.md b/documentation/projects/proposals/additional_search_views/20230719-implementation_plan_additional_search_views.md index 9a36910e3f6..9f0f2adf7fd 100644 --- a/documentation/projects/proposals/additional_search_views/20230719-implementation_plan_additional_search_views.md +++ b/documentation/projects/proposals/additional_search_views/20230719-implementation_plan_additional_search_views.md @@ -170,7 +170,7 @@ The flag should be switchable, and off by default. We can reuse the search store as is for these pages. -_Previously, frontend search store had a `searchBy` filter that allowed to +_Previously, the frontend search store had a `searchBy` filter that allowed to search within the `creator` field. When `searchBy` value was set, the API `q` parameter was replaced with the `=` API query parameter. This filter was removed because `searchBy` is not strictly a filter that can be