Load the schedule export code when export is requested
The spreadsheet export dependency adds work to every schedule visit even though the baseline user never exports.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Code splitting · Failure states
Estimated field mix
- Frontend50%
- Performance engineering30%
- Accessibility20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional repair coordinator opens a week containing 2,000 jobs. The initial page loads, but filtering and selecting a job can freeze the interface. Build a synthetic scheduling screen with keyboard operation before measuring changes.
Setup prerequisites
- Create a local schedule UI with 2,000 synthetic jobs, long labels, empty results and deterministic responses.
- Record browser version, viewport, device emulation, CPU/network throttling and build mode for every comparison.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Move export-only code behind an explicit load boundary and preserve the generated file contents.
- Show a keyboard-accessible loading state and prevent duplicate export starts while the module loads.
- Handle module-load failure with a retry action without losing selected filters.
Implementation constraints
- Compare initial transfer and parse work in the same production build configuration; do not defer code required to display the schedule.
Verification to include
- Verify the initial workflow makes no export-module request, then trigger export and compare the file with the baseline fixture.
- Fail the module request once and confirm retry succeeds with the original filter state.
Deliverables
- Deferred export implementation, network comparison and failure regression
Rollout and recovery
Keep a loading-boundary switch in the exercise; revert to eager loading if export compatibility fails.
Value of the work
For the engineer: Connect bundle, rendering and interaction measurements to user-visible behavior without losing accessibility.
For the team: Produce a bounded performance investigation and regression workflow for dense operational interfaces.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.