fix: update featuresGeojsonChange
event to match new geojsonChange
behavior
#479
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.
Follows on from #466
Changes:
drawMode
- theclickFeatures
functionality dispatches geojson & area events which should stay consistent with recent changes we've made to event dispatching - so we're deprecatingfeaturesAreaChange
event and instead setting"area"
directly on thefeaturesGeojsonChange
event data "properties"areaUnit
prop and simply sets both"area.squareMetres"
and"area.hectares"
anywhere we calculate the area (these field names & new number type are more consistent with ODP Schema too)