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
Currently, when unset features are serialized, this will lead a null value at the JavaScript/JSON side which leads to lot of boilerplate null checking code.
It would be great to allow how unset features should be treated.
For example, for a multi-valued feature, I would like the JSON object to have an empty array instead of null, so I do not have to check in JavaScript for null before accessing it.
The text was updated successfully, but these errors were encountered:
Currently, when unset features are serialized, this will lead a null value at the JavaScript/JSON side which leads to lot of boilerplate null checking code.
It would be great to allow how unset features should be treated.
For example, for a multi-valued feature, I would like the JSON object to have an empty array instead of null, so I do not have to check in JavaScript for null before accessing it.
The text was updated successfully, but these errors were encountered: