You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the map trace fitbounds attribute to be an enum instead of boolean.
Why should this change be made?
This will allow us to treat fitbounds in a similar way to the corresponding attribute for geo traces. Right now the auto-fit for map traces skips choropleths because those would have to be handled at a different point in the code. As such, the attribute could just be on/off. If we add choropleth support in the future, the attribute schema will have to change. By making this change now before the release of v4.0, we won't have to worry about breaking anything.
Description
Update the map trace
fitboundsattribute to be an enum instead of boolean.Why should this change be made?
This will allow us to treat
fitboundsin a similar way to the corresponding attribute for geo traces. Right now the auto-fit for map traces skips choropleths because those would have to be handled at a different point in the code. As such, the attribute could just be on/off. If we add choropleth support in the future, the attribute schema will have to change. By making this change now before the release of v4.0, we won't have to worry about breaking anything.Scope
Notes
fitboundsto map traces, but it's built against master instead of v4.0