-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
Optmise Disbursement layers on map #35516
Conversation
@ajeety4 The How about the following (note that I haven't tested it) - I removed the
|
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.
Looks good! Just a minor comment.
Hey Charl , this is great point. The iteration is being done twice. While looking through it, I did end up reusing the existing data structure and made some improvements. Changes are here |
Product Description
Updates logic to create a single disbursement layer for lines connecting cases and mobile workers on map instead of one layer for each line. This significantly improves the map performance for higher assignments(>1k).
Technical Summary
Ticket
Feature Flag
Microplanning.
Safety Assurance
Safety story
Behind a feature flag and changes only relates to disbursement. Tested on local.
Automated test coverage
QA Plan
None
Rollback instructions
Labels & Review