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
Is this behavior by design? It looks odd. And needs some additional client-side cumbersome handling when expecting feature properties to be possibly null instead of "null".
The text was updated successfully, but these errors were encountered:
Bernoulli-IT
changed the title
GeoJson Feature property with null value becomes "null" as a string when querying rendered features
GeoJson Feature property with null value becomes "null" as string literal when querying rendered features
Sep 9, 2020
mapbox-gl-js version: 1.11.0
browser: Chrome
Steps to Trigger Behavior
Expected Behavior
The value should remain as null.
Actual Behavior
The value became "null" as a literal string.
Example
Start of a GeoJson file.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": "NLWMO002360566200097",
"properties": {
"bridgeDetails.vild": null,
...
Property inspected with Chrome inspector:
bridgeDetails.vild: "null"
Is this behavior by design? It looks odd. And needs some additional client-side cumbersome handling when expecting feature properties to be possibly null instead of "null".
The text was updated successfully, but these errors were encountered: