Skip to content

Experiments Portlet — swap the List to the server-side contract #37007

Open

Description

@oidacra

Description

#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.

Scope

Boundary check

Only two places should change in existing code: the data-access service and the store's load event handler. No existing component should need touching — the one enumerated exception is the two new toolbar filter controls (creator, running date range), which are new components this issue adds. If any other component needs a change, #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).
  • URL behavior is byte-identical for all pre-existing params: same names, same defaults-omitted rule, same deep-link restoration (the E2E deep-link spec from Experiments Portlet — E2E test suite (incl. flag-off regression of the old flow) #37006 passes unchanged). The three new params (created_by, running_from, running_to) are additive and follow the same defaults-omitted rule.
  • Page column shows the enriched title/path; the interim lookup is deleted.
  • Status counts come from the API and reflect the whole filtered set.
  • Site scoping uses the siteId param; switching site refetches.
  • Diff touches only the data-access service, the store load handler, the two new toolbar filter controls, and deleted interim code.
  • Filter by creator works server-side via created_by; filter by running date range works server-side via running_from/running_to with inclusive overlap semantics; both compose with every other filter and are reflected in counts and totals.
  • Jest specs updated: load handler asserts outgoing params per state.

Priority

Medium — unblocks scale, not features.

Additional Context

Activity

  1. added theissue type on Aug 11, 2026
  2. moved this from New to Current Sprint Backlog in dotCMS - Product Planningon Aug 11, 2026
  3. github-actions commented on Aug 27, 2026

    @github-actions
    Contributor
  4. moved this from Current Sprint Backlog to Spec in dotCMS - Product Planningon Aug 31, 2026
  5. moved this from Spec In Progress to Spec In Review in dotCMS - Product Planningon Aug 31, 2026
  6. moved this from Spec In Review to In Progress in dotCMS - Product Planningon Aug 31, 2026
  7. 4 remaining items

  8. moved this from In Progress to Next 2-4 Sprints in dotCMS - Product Planningon Sep 8, 2026
  9. moved this from Next 2-4 Sprints to Future in dotCMS - Product Planningon Sep 8, 2026
  10. oidacra commented on Sep 18, 2026

    @oidacra
    MemberAuthor

    Dependency status: #36823 is not merged.

    The Additional Context section reads Depends on: #36823 (merged, including permission filtering). That parenthetical is not accurate today. Verified against main:

    So this issue is still blocked on #36823, and the two SQL fixes it names have not landed either.

    Heads-up on the two toolbar controls. Scope item 2 asks for a creator filter and a running-date-range filter. #37307 is adding both now, client-side, against the payload as it stands. When this issue is picked up they will already exist, so the work is swapping them onto the server-side parameters rather than building them.

    One divergence will need a deliberate decision at that point: #37307's time filter compares the experiment's scheduled start, while #36823's running_from/running_to compare the running window — actual runs, or the scheduled window when the experiment never ran — with both bounds inclusive. For an experiment that has already run those answer different questions, and the change is visible to anyone who had the filter applied before the swap.

    The creator parameter needs no reconciliation: #37307 already names it created_by.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions