1.9 KiB
1.9 KiB
type, project, status, ticket, title, systems, workstreams, people, related, updated, tags
| type | project | status | ticket | title | systems | workstreams | people | related | updated | tags | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| work-item | fidelity | backlog-ready | PDIAP-12284 | Remove UIKit wrapping from XFlow |
|
|
|
|
2026-05-08 |
|
PDIAP-12284 - Remove UIKit wrapping from XFlow
Status
- Reopened after rollback.
- Quy already moved this story into the next sprint (
26Q2.6); leave it in To Do until the sprint starts on Thursday. - Jeff directed David to do this UIKit-removal work and
PDIAP-15836dismissal/lifecycle work in the same branch because both are disruptive enough to require consumer testing.
Context
- This is the original story for removing the UIKit wrapping.
- Current relationship to track:
PDIAP-12284should be handled withPDIAP-15836in the same implementation branch. David identified a possible minimalPDIAP-15836fix path that does not require removingUIHostingController, but Jeff prefers combined branch work because both changes require consumer testing.
Historical Slack Context
- November 21, 2025 Slack context says David created
PDIAP-12284andPDIAP-12285to cover remaining UIKit-removal work inside XFlow after reviewing open Sendable and XFlowViewMaker-track stories. - That same backlog refinement closed out pending XFlowViewMaker stories that were no longer needed.
- Current Mattermost context supersedes the old standalone refinement framing: this story is now reopened after rollback and should be handled together with
PDIAP-15836.
Sequencing
- Work can begin, but merge/release should wait until the REST-transition consumer-validation window has completed.
- Keep the implementation branch up to date with
mainwhile waiting for approval to work with consumers and merge.