geojson: null
json into non-pointer Feature/FeatureCollection will set them to empty
#145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #144
If you have
{ feature: null }
and you're trying to unmarshal it into something likeyou'd get a panic. This fix sets
Struct.Feature
to an empty object. I think this is the correct behavior as you might have{ isFeature: true, feature: null }
and you're code would checkisFeature
first.If you really care about if it's null vs. empty you should model your data as
the check
Struct.Feature != nil