Open rikukissa opened 1 month ago
@jpye-finch
Currently we fetch all workqueues at the same time when the app is loaded.
Is there value in that or could we load each of them dynamically when that workqueue page is opened? This could simplify the workqueue loading, just an thought at this point though. If you don't have internet you can see the workqueues you have opened earlier.
Yes it could work. Would the experience not be same as we have to day? When you navigate between workqueues after login and initial load. You see the latest state of the workqueue whilst we check for changes.
As long as you can still see your assigned records so you can work offline. We are good imo
This is also functional and based on experiment ascertain estimate.
Implement country config configurable workqueues. Configuration should leverage advanced searches search parameters
https://opencrvsworkspace.slack.com/archives/GHCFF9M6X/p1717000313286379
Dev tasks
GET /workqueues
to country-config to serve each of the workqueues[ ] Let config fetch this and serve it to client via GraphQL Gateway. Create a
useWorkqueueConfiguration
React hook that both fetches the payload but also stores it for offline. All workqueue related logic should be bundled here.[ ] Create a new route to client as
/workqueues/:slug
which renders a dummy view fromsrc/views/Workqueue/WorkqueueView.tsx
[ ] Update the sidenav to render workqueues based on the workqueue-configuration
[ ] Build the WorkqueueView. Use gateways
searchEvent
with Apollos use-hook with the correct configuration from