Bug Report
Describe the bug
legend store and selected features store are designed to stay in sync -- when there are updates on a particular map/interactive layer. if somehow the elgend store of another map (thats not selected/current) gets updated then selected features will not reflect that update until its been reopened and interacted with, triggering a sync subcription
To Reproduce
navigate to us_states map
manually edit the legend data in the us_counties map localstorage
navagate to us_counties map
note the changes you made manually are not present
edit legend tiem > all syncs up
Proposed solution
on map navigate > sync legend stores and selected features store
this will prevent unnecessarily heavy updates on all changed to legend store but still ensure the map the user is using is in sync
alt => if a user navigates you could sync that whole stores, not just for the map being opened
Expected behavior
should remain in sync
Actual Behavior
fall out of sync in edge cases, not clear if there are user action lines that would lead to this behavior at least
Screenshots
Environment (please complete the following information):
Additional context
Bug Report
Describe the bug
legend store and selected features store are designed to stay in sync -- when there are updates on a particular map/interactive layer. if somehow the elgend store of another map (thats not selected/current) gets updated then selected features will not reflect that update until its been reopened and interacted with, triggering a sync subcription
To Reproduce
navigate to us_states map
manually edit the legend data in the us_counties map localstorage
navagate to us_counties map
note the changes you made manually are not present
edit legend tiem > all syncs up
Proposed solution
on map navigate > sync legend stores and selected features store
this will prevent unnecessarily heavy updates on all changed to legend store but still ensure the map the user is using is in sync
alt => if a user navigates you could sync that whole stores, not just for the map being opened
Expected behavior
should remain in sync
Actual Behavior
fall out of sync in edge cases, not clear if there are user action lines that would lead to this behavior at least
Screenshots
Environment (please complete the following information):
Additional context