Robert Bond
0de9268255
## Summary This PR merges the completed new-appeal refactor stream (Slices 1–8) into SIPS-Development. This refactor was executed in controlled slices with regression validation at each step. ## Scope Structural and readability improvements only: - XML/form derivation extraction - payload and file helper extraction - side-effect facade introduction - BuildSection and BuildCheckSection decomposition - BuildCheckRow formatter map refactor - nested prop boundary cleanup - start-flow cleanup (CreateCase / AboutYou) ## Behaviour No intended behavioural changes. The following were explicitly preserved: - S78 journey behaviour - payload shapes and field names/ids - HASCAS mapping logic - appellant/agent branching - validation rules and messages - redirect/query parameters (`lpa`, `apt`, `id`) - navigation and side-effect sequencing - EN/CY output parity ## Validation Full regression has been performed on: - start flow (CreateCase / AboutYou) - save and resume flows - file upload handling - check answers rendering - submit/finalisation sequence - confirmation flow - CRM insertion path - EN/CY parity Additional checks: - docsOffline branch behaviour - completion and partial-save email paths - negative-path validation scenarios - lint (warnings baseline unchanged) ## Risk Low: - changes are structural only - no business logic changes - no contract changes ## Rollback Safe rollback via reverting this merge commit. ## Notes This refactor reduces coupling and prepares the new-appeal flow for future appeal-type expansion. Related work items: #22570, #22576, #22577, #22583, #22586, #22587, #22588, #22590
19 lines
514 B
Markdown
19 lines
514 B
Markdown
# Database Migration Workflow
|
|
|
|
1. Understand the desired schema or data change.
|
|
2. Inspect current data model, queries, and dependent code.
|
|
3. Identify:
|
|
- forward migration steps
|
|
- backward compatibility concerns
|
|
- rollback considerations
|
|
4. Implement or propose the minimal safe migration path.
|
|
5. Review for:
|
|
- data integrity
|
|
- ordering issues
|
|
- application compatibility
|
|
- deployment timing risk
|
|
6. Summarize:
|
|
- schema/data changes
|
|
- impacted code paths
|
|
- rollout / rollback notes
|