Thanks to @deathsh0ot we finally been able in this third attempt to introduce the bubble map chart along with the existing map chart by refactoring code and optimizing the execution flow.
We came to the conclusion that map based chart is unlike any other chart and it should have it's proper mechanics. It should be able to compute projection data once and pass it the additioinal components (bubbles for our case). That's why we decided to implement it as a context provider.
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update
Checklist:
[x] I have done the work for both react and vue
[X] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation (Storybook)
[x] I have added unit tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
Motivation
Thanks to @deathsh0ot we finally been able in this third attempt to introduce the bubble map chart along with the existing map chart by refactoring code and optimizing the execution flow.
We came to the conclusion that map based chart is unlike any other chart and it should have it's proper mechanics. It should be able to compute projection data once and pass it the additioinal components (bubbles for our case). That's why we decided to implement it as a context provider.
Type of change
Please delete options that are not relevant.
Checklist: