49 lines
1.3 KiB
Markdown
49 lines
1.3 KiB
Markdown
---
|
|
type: daily
|
|
project: fidelity
|
|
date: 2026-04-21
|
|
status: active
|
|
focus: [rest-migration]
|
|
work-items: [pdiap-15838]
|
|
blockers: []
|
|
tags:
|
|
- daily
|
|
- fidelity
|
|
updated: 2026-04-21
|
|
---
|
|
|
|
# 2026-04-21
|
|
|
|
## Focus
|
|
|
|
- Continue `PDIAP-15838` Apollo-removal cleanup.
|
|
|
|
---
|
|
|
|
## Work Done
|
|
|
|
- Cleaned up the active production model layer so it no longer depends on Apollo-generated models for the current path.
|
|
|
|
---
|
|
|
|
## Findings
|
|
|
|
- The model-decoupling step for `PDIAP-15838` is now in a cleaner state.
|
|
- The next focus should shift to the remaining Apollo-dependent runtime and infrastructure surface: init/session coupling through `NetworkClient`, Apollo-generated/runtime code that is no longer needed, and Apollo-specific tests/scripts/build wiring.
|
|
- Any Apollo dependency that remains only through PicoSDK should be treated separately from source-level cleanup.
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
- Confirm the remaining `NetworkClient` / init-session Apollo dependencies and whether any AppSync config APIs still need compatibility handling.
|
|
- Identify the runtime Apollo files that can now be removed safely after the model cleanup.
|
|
- Remove Apollo-only tests, mocks, codegen scripts, and build wiring once runtime references are gone.
|
|
- Treat any transitive PicoSDK Apollo dependency as a separate dependency-exit step.
|
|
|
|
---
|
|
|
|
## Blockers
|
|
|
|
- None currently.
|