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
Using 'filter': ['!', ['config', 'test', 'basemap']]config.js#L81 evaluate() is never called and always returns false, even when the config is set to true.
Workaround:
config expression inside style properties is evaluated properly (when created with createPropertyExpression ) 'visibility': ['case', ['config', 'test', 'basemap'], 'none', 'visible']
IMHO the filter has to be updated anyway. Right now we can't use the new expression syntax when using the old deprecated filter keywords like == or in and so on. Maybe add an addLayer option to make it a data driven expression with new syntax only, which supports config or just completely ditch support for the deprecated syntax.
If you really want to keep support for the old syntax, maybe add an indicator for using the new syntax with filter: ['v2', [...]]
The text was updated successfully, but these errors were encountered:
mapbox-gl-js version: v3.3.0
browser: irrelevant
Steps to Trigger Behavior
Add config schema to map style
Using
'filter': ['!', ['config', 'test', 'basemap']]
config.js#L81 evaluate() is never called and always returns false, even when the config is set to true.Workaround:
config expression inside style properties is evaluated properly (when created with createPropertyExpression )
'visibility': ['case', ['config', 'test', 'basemap'], 'none', 'visible']
IMHO the filter has to be updated anyway. Right now we can't use the new expression syntax when using the old deprecated filter keywords like
==
orin
and so on. Maybe add an addLayer option to make it a data driven expression with new syntax only, which supports config or just completely ditch support for the deprecated syntax.If you really want to keep support for the old syntax, maybe add an indicator for using the new syntax with
filter: ['v2', [...]]
The text was updated successfully, but these errors were encountered: