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
After sync with the app architecture team, we decided to pass the formatting information to the visualization by attaching it as meta information to the column data type which can be used in the toExpression function of the visualization.
To pass it to the renderer we should use a unified "dimension" data type for the arguments which can be re-used across all visualization expression renderers (this will also make integration with the current visualize infrastructure easier because it's following the same approach). By doing so we can treat formatting information exactly like labels and don't have to change things about the data table type just yet which keeps Lens usage of expressions closer to current visualize and Canvas.
Default formatting options passed as meta information as part of the data table column (see #38874 ) will be postponed till canvas also has formatting support and patterns for how to structure this information have emerged to not prematurely pollute the data table type with Lens-specific things.
The text was updated successfully, but these errors were encountered: