You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#36989 ships the list against GET /api/v1/experiments as it exists today, computing paging, sorting, filtering, status counts and site scoping client-side — an explicit, documented interim. This issue replaces that interim with the server-side contract from #36823, and is filed together with #36989 on purpose so the interim cannot quietly become permanent. It lands whenever #36823 does; nothing else waits on it.
The URL param contract was designed to be final from day one, so this swap changes where the params are applied, not what they are called.
Only two places should change: the data-access service and the store's load event handler. No component should need touching. If one does, #36989's service boundary was drawn wrong — flag it in review instead of patching around it.
Acceptance Criteria
The list issues one request per view change carrying the server-side params; no client-side slicing/sorting/filtering remains (interim utilities deleted).
Description
#36989 ships the list against
GET /api/v1/experimentsas it exists today, computing paging, sorting, filtering, status counts and site scoping client-side — an explicit, documented interim. This issue replaces that interim with the server-side contract from #36823, and is filed together with #36989 on purpose so the interim cannot quietly become permanent. It lands whenever #36823 does; nothing else waits on it.The URL param contract was designed to be final from day one, so this swap changes where the params are applied, not what they are called.
Scope
page,per_page,orderby,direction,filter,status,siteId).pageTitle/pageUrl/ site in the Page column, deleting Experiments Portlet — Screen 1: portlet base + site-wide List #36989's interim client-side page lookup.totalRecordsfrom the response body (pagination.totalEntries), not theX-Pagination-*headers.name+statusmalformed SQL;pageId+multi-status precedence).Boundary check
Only two places should change: the data-access service and the store's load event handler. No component should need touching. If one does, #36989's service boundary was drawn wrong — flag it in review instead of patching around it.
Acceptance Criteria
siteIdparam; switching site refetches.Priority
Medium — unblocks scale, not features.
Additional Context