30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
# XFlowViewMaker
|
|
|
|
## Role
|
|
|
|
XFlowViewMaker is the adapter layer between XFlowSDK and consuming app/framework integration. It is under evaluation for reduction or removal.
|
|
|
|
---
|
|
|
|
## Durable Context
|
|
|
|
- Historical release work often required bumping XFlowViewMaker alongside XFlowSDK before consumer validation was possible.
|
|
- XFlowViewMaker was a recurring source of coupling between XFlow changes and Fid4 or flagship rollout.
|
|
- Historical Slack evidence shows that version bumps through XFlowViewMaker were often blocked by external pipeline or dependency issues rather than pure feature regressions.
|
|
|
|
---
|
|
|
|
## Integration Implications
|
|
|
|
- When a fix exists in XFlowSDK but is not visible in consumer validation, check whether XFlowViewMaker or downstream pinned versions are blocking adoption.
|
|
- If the issue involves version propagation into Fid4, treat XFlowViewMaker as part of the release path unless direct-consumption work has replaced it.
|
|
- Questions about removing or collapsing the layer should be evaluated against current consumer integration patterns, not just local SDK behavior.
|
|
|
|
---
|
|
|
|
## Historical Signals From Slack
|
|
|
|
- XFlowViewMaker version bumps into flagship frequently surfaced `PreviewMacros.SwiftUI`, Apex, or pipeline compatibility issues.
|
|
- Historical context shows growing pressure to reduce XFlowViewMaker-specific indirection and move toward simpler consumer paths.
|
|
- Slack history also shows that tutorials and release steps around XFlowViewMaker were easy to misunderstand, which made version propagation a repeated risk.
|