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
The feature string id is present on the feature object and properties are restitued as provided (same type, same content) by the source GeoJSON (and as specified in the GeoJSON specifications)
Actual Behavior
String identifier (id) is missing on the features
Arrays and objects are stringified
Related issues
It seems to be a recurring issue on different levels:
Most of them didn't had advancement for months or years.
There is even a merged pull request hardening this behavior #7106 (String identifier is a really common use case so why force number ID instead of ensuring string are properly handled)
The text was updated successfully, but these errors were encountered:
Hi @noirbizarre, thanks for the report. This is definitely an issue we want to work on, but I don't understand if there's something new you're reporting here? This looks like a duplicate of #2434 and #2716. Feel free to re-open if I've missed something.
mapbox-gl-js version: 0.50.0
browser: Any
Steps to Trigger Behavior
id
on features andArray
orObject
as propertiesfeatures
property or use anyquery*Features
helperid
and the stringifiedproperties
on featuresLink to Demonstration
https://jsfiddle.net/dcwp7xu4/1/
Expected Behavior
The feature string
id
is present on the feature object andproperties
are restitued as provided (same type, same content) by the source GeoJSON (and as specified in the GeoJSON specifications)Actual Behavior
id
) is missing on the featuresRelated issues
It seems to be a recurring issue on different levels:
properties
#4380id
property on internal GeoJSON objects #3210Most of them didn't had advancement for months or years.
There is even a merged pull request hardening this behavior #7106 (String identifier is a really common use case so why force number ID instead of ensuring string are properly handled)
The text was updated successfully, but these errors were encountered: