Skip to content

fix(series): include scopeId in PUT payload#169

Merged
sharmeebuilds merged 1 commit into
devfrom
chore/config-fixes
May 28, 2026
Merged

fix(series): include scopeId in PUT payload#169
sharmeebuilds merged 1 commit into
devfrom
chore/config-fixes

Conversation

@sharmeebuilds
Copy link
Copy Markdown
Collaborator

Summary

  • ESP returns scopeId on GET series but SERIES_DATA_FILTER stripped it on PUT, so scope membership was being dropped on every series update / publish / unpublish / archive.
  • Added scopeId to SERIES_DATA_FILTER as submittable: true, updatable: true, cloneable: false (clones should derive scope from the active scope context, not the source series).
  • Threaded scopeId from the loaded canonical SeriesApiResponse into SeriesForm's buildApiPayload so it survives both filter passes (the form-level filter and prepareEspSeriesPutPayload inside the API service).
  • SeriesDashboard's publish/unpublish/archive flows already pass the full SeriesApiResponse, so the filter change covers them automatically.

Test plan

  • Edit an existing series in EMC, hit Save — verify the PUT body in DevTools includes scopeId matching the value returned on GET.
  • Publish, unpublish, and archive an existing series from SeriesDashboard — verify each PUT includes scopeId.
  • Create a new series, then publish it — verify the second (publish) PUT includes the scopeId returned by the create call.
  • Confirm series scope assignment is preserved after each of the flows above (re-fetch the series and check scopeId).

🤖 Generated with Claude Code

ESP returns scopeId on GET but SERIES_DATA_FILTER stripped it on PUT,
causing scope membership to be lost on series update/publish/unpublish/
archive. Add scopeId to the filter (updatable, not cloneable) and thread
it from the loaded canonical response into SeriesForm's buildApiPayload.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@sharmeebuilds sharmeebuilds merged commit 0140da6 into dev May 28, 2026
3 checks passed
@qiyundai qiyundai mentioned this pull request May 29, 2026
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants