The map view is behind a map_view cargo feature on rerun-cli, which is enabled in release build but not in default build (aka when building from source). This leads to a footgun where people don't see a map when they expect one. We should warn the user when that happens, indicating that the map_view feature needs to be enabled.
The proposed mechanism for that is to have a store subscribers that reacts to some specific indicator components, and emit warnings as required.
Level 1: hard code GeoPoints and GeoLineStrings (subject to bitrot, eg when we introduce GeoPolygons
Level 2: use the information already contained in attribute.docs.view_types to populate the reflection structures, and use said structure to generate warnings for all kinds of view that might be missing.
.
.
.
Level ∞: "unsupported data, click here to download the Map view plugin"
The map view is behind a
map_viewcargo feature onrerun-cli, which is enabled in release build but not in default build (aka when building from source). This leads to a footgun where people don't see a map when they expect one. We should warn the user when that happens, indicating that themap_viewfeature needs to be enabled.The proposed mechanism for that is to have a store subscribers that reacts to some specific indicator components, and emit warnings as required.
Level 1: hard code
GeoPointsandGeoLineStrings(subject to bitrot, eg when we introduceGeoPolygonsLevel 2: use the information already contained in
attribute.docs.view_typesto populate the reflection structures, and use said structure to generate warnings for all kinds of view that might be missing. . . .Level ∞: "unsupported data, click here to download the Map view plugin"