fix: trigger featureChanged on feature props change #1201
Merged
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.
#1196 intended to add a call to
featureChanged
any time a feature wasadd()
ed with modified properties, however it has a bug in that the check came after assignment.An alternative to this fix would be to move the assignment inside the
if()
body, but that could break other code that depended on referential equality after callingadd()
.I verified the fix by hacking the demo to include a button which modified a property on a feature, and also hacked the stylesheet to render that property as a label. Code here: petermoz@132d2d2
I had a look at adding tests but couldn't figure out how to best get access to
store.getChangedIds
from the the API test. Happy to add tests if you have a suggestion about accessing the store.