Closed ndegwamartin closed 5 months ago
Is this cleanup only or do we get a functional benefit from this change?
Is this cleanup only or do we get a functional benefit from this change?
This is related to the findings here https://github.com/opensrp/fhircore/issues/2942
This should be code cleanup plus it will improve the sync notification UX.
Note: The issue https://github.com/opensrp/fhircore/issues/2942 is still blocked by https://github.com/google/android-fhir/issues/2472
Describe the feature request. We need to migrate from using
SyncJobStatus
to usingCurrentSyncJobStatus
which has both work state and SyncJobStatus state representations.Additional context This follows the upgrade SDK libraries PR https://github.com/opensrp/fhircore/pull/2825 changes
Acceptance criteria A check list of all things to verify once the implementation by the engineer is complete
Area path A list of ordered steps in the app on usage of the feature to support anyone testing it e.g. Code reviewer, QA e.g.
Implementation plan (For Engineers) The plan for implementing the solution e.g. via a description or a check list for the various ordered tasks that will need to be completed. i.e. Describe how you intend to solve the problem