fix feature.setProperty()
to create a new property if it doesn't already exist
#10775
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 #10773
This fixes the regression in
setProperty()
for unknown propertyId by:JsonMetadataTable
to create a property if it doesn't existPropertyTable
to create aJsonMetadataTable
if it doesn't exist, then usingthis._jsonMetadataTable.setProperty()
to create the new property if it doesn't exist.Other notes:
Cesium3DTileBatchTable
is inconsistent betweengetProperty
andsetProperty
.Sandcastle example -- the property will now be created at runtime, so the console will log
This is a new property
several times, instead ofundefined
like it does onmain
.