-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#2764] Resolve cases concurrently when loading the case list #1407
Conversation
d186da7
to
570b63a
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1407 +/- ##
===========================================
- Coverage 94.88% 94.84% -0.05%
===========================================
Files 1045 1045
Lines 38692 38740 +48
===========================================
+ Hits 36714 36744 +30
- Misses 1978 1996 +18
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
5c25456
to
a9d8902
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed CaseListService
could go in a dedicated service module, now that we're also collecting the service functions from the deleted openzaak.cases
.
a9d8902
to
bd97485
Compare
Resolving cases involves several sequential network requests, which creates a lot of latency when loading a lost of cases. This commit runs the resolving concurrently, and also centralizes the logic in the CaseListService.
bd97485
to
9c76b5b
Compare
Taiga 2764.