Skip to content

Adapt frontend to batch edit and export endpoint changes#3192

Draft
markus-moser wants to merge 6 commits into2025.4from
feature/execution-engine-batch-edit-improvements
Draft

Adapt frontend to batch edit and export endpoint changes#3192
markus-moser wants to merge 6 commits into2025.4from
feature/execution-engine-batch-edit-improvements

Conversation

@markus-moser
Copy link
Copy Markdown
Contributor

@markus-moser markus-moser commented Mar 23, 2026

Summary

  • Update folder patch/export endpoints to use path parameter for folder ID (moved from request body), matching backend PR [Execution Engine] Batch edit all assets fails with a lot of items  studio-backend-bundle#1557
  • Add classId parameter for selected element CSV/XLSX exports of data-objects
  • Fix download URL for multi-step export jobs to use child job ID via JobButtonCustomizationContext
  • Improve job progress handling: prevent backwards progress jumps, recreate polling fallback for child jobs, stop processing stale data after child job transitions
  • Add CombinedProgressJobHandler subclass for multi-step jobs where some steps have granular progress and others complete instantly — instant steps show an indeterminate spinner with step description, gradual steps show a smooth progress bar
  • Remove DirectEdit endpoints from OpenAPI schema

Test plan

  • Asset folder batch edit: verify indeterminate spinner during step 1, smooth progress bar during step 2, successful completion
  • Data object folder batch edit: same as above
  • Asset selected elements batch edit (multi-select): verify still works
  • Data object selected elements batch edit: verify still works
  • CSV folder export: verify export completes and download works with child job ID
  • CSV selected elements export: verify classId is sent for data-objects
  • XLSX folder export: same as CSV folder
  • XLSX selected elements export: same as CSV selected
  • ZipUploadJob: verify 2-step progress still works correctly
  • Smoke test other jobs (delete, clone, tag assign) for regressions

- Update folder patch endpoints to use path parameter for folder ID
- Update folder export endpoints (CSV/XLSX) to use path parameter
- Add classId for selected element exports of data-objects
- Fix download URL to use child job ID via JobButtonCustomizationContext
- Improve job progress handling: prevent backwards progress, recreate
  polling for child jobs, stop processing after child job transition
- Add CombinedProgressJobHandler for multi-step jobs with mixed progress
- Show indeterminate spinner with step descriptions during instant steps
- Remove DirectEdit endpoints from OpenAPI schema
@markus-moser markus-moser added this to the next milestone Mar 23, 2026
markus-moser and others added 5 commits March 23, 2026 15:51
- Widen objectReference type to string | number in format path helpers
- Pass required createPredefinedMetadata body to create mutation
- Extract handler interfaces to separate file to fix max-lines lint rule
Widen formatedPath to string | number and cast to String() at usage sites.
… jobs

- Show step counter only for jobs with more than 1 step (job-view.tsx)
- Add two-step support to DownloadJob for folder CSV/XLSX export; download
  uses child jobRunId automatically via transitionToChildJob
- Add totalSteps: 2 to CombinedProgressJobHandler in folder batch-edit jobs
  to fix step 0/1 and step 2/1 display bugs
- Prevent backend messages from overwriting handler-owned currentStep and
  totalSteps in processUpdate; handler constructed with explicit totalSteps
  is the sole source of truth for the step counter
- Reset hadGradualProgress on transitionToChildJob in CombinedProgressJobHandler
- Fix stale stepDescriptionKey after child job transition by including it in
  the transitionToChildJob store update
- Compute compound progress for sub-stepped child jobs: combines backend
  currentStep/totalSteps with within-step percentage into a single 0-100 value
- Add 'Creating export file' translation key
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 3, 2026

@markus-moser markus-moser changed the base branch from 1.x to 2025.4 April 7, 2026 14:38
@markus-moser markus-moser removed this from the 2025.4 milestone Apr 7, 2026
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.

1 participant