vectorBase: a value that cannot be evaluated is the property's default, as in MapLibre

A paint or layout value that throws for a feature (a type that does not
fit, step or interpolate over what is not a number) or comes to null,
undefined or NaN is now the property's default, and a legacy function's
miss is its default, else the property's; only a filter that cannot be
evaluated leaves the feature out. The canvas still never keeps the last
feature's colour or width. A background colour given as rgba numbers is
the style's background rather than none.
This commit is contained in:
Sameh Khamis committed 2026-11-11 20:05:25 -08:00
1 parent 7b07ddeefd
commit 7f500a551c
5 files changed
+181 -58

No files matched your search

+4 -2
View File
@@ -5,8 +5,10 @@
* value is compiled once into a function of `{zoom, properties, type, id}`
* (`type` is `'Point'`, `'LineString'` or `'Polygon'`). Compiling throws an
* {@link Unsupported} for what is not covered, so the caller skips the layer;
* a compiled function that meets a value it cannot handle throws one too, so
* the caller skips the feature. Nothing here guesses.
* a compiled function that meets a value it cannot handle throws one too: a
* filter that throws leaves the feature out, a paint or layout value that
* throws is the property's default (as MapLibre takes it). Nothing here
* guesses.
*/
/** What the painter does not evaluate: the layer or feature is skipped. */