fix: sometimes changes to the draggable prop don't get propagated #994
+2
−5
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.
This pull request fixes an issue where a change to the draggable prop would not make the map draggable by not omitting the prop inside the
shouldComponentUpdate
prop.If we change the prop but there is no other prop change the map behavior won't get updated, as that is done inside the
componentDidUpdate
function.You can see the issue reproduced in this sandbox: https://codesandbox.io/s/distracted-wright-hrs51?file=/src/App.js
When you make the map draggable only the last map becomes draggable as there is another prop change, while the first 2 can't be dragged (the second one is expected as the code in
componentDidUpdate
omits those).Fixes #978