Hot answers tagged

3

Are you using the VL Bridge? If so, there is an undocumented method for the category widget's bridge: enableColorMapping. If the viz bridged to your as-category-widget has a color ramp, it will add the color to the categories automatically. Keep in mind that it's undocumented, so it might change in the future without notice. const bridge = new AsBridge....


2

As explained in CARTO documentation, Airship is a design framework to build (geospatial) applications. It works nicely with CARTO VL and CARTO JS, but you could add it to any of your projects. Basically, it helps you to apply already designed layouts (sidebars, panels, toolbars...), components (widgets, legends, sliders...), and styles (colors, typography...)...


2

Main culprit of the breaking change here. The selection is a bit more complex now, because of categorical data support. The event.detail is an object with several props. In event.detail.selection there's the "old" selection format, so you can just change to: widget.addEventListener('selectionChanged', event => { this.$emit( '...


2

You can change the properties of the widget right after the append call. For instance, you could change visibleCategories and it should work. If you need to read the properties back, you have to wait until the next tick. From a VL <--> Airship perspective, the widget will update on every update event on the layer it's bridged to. You could listen to that ...


2

There is a non documented property for this. In the histogram is called noDataHeaderMessage https://github.com/CartoDB/airship/blob/master/packages/components/src/components/as-histogram-widget/as-histogram-widget.tsx#L156


Only top voted, non community-wiki answers of a minimum length are eligible