fix: don't mutate data in fromData
, clone instead
#602
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.
Summary
always clone the input data in
fromData
so that the input is not mutatedDescription
in the clear case,
fromData
would setthis._data = pointGroups
,which made the pointer the same as the one for the parameter
this._data
is internally mutated, this would cause the inputparameter to also be mutated as a side-effect
this input mutation side-effect is likely unintended, so patched it so
that the data is cloned in all cases, not only in the append case
this._data
is set to an empty array bythis.clear()
, so this is equivalent to[].concat(pointGroups)
,which will result in them all being cloned
Misc Notes
Fixes agilgur5/react-signature-canvas#56
Credits to @Zwyx for discovering this in the above issue
Can see that issue for some manual testing I did around this cloning as well as how I found the bug here