fix: Stop throwing errors when calling removeToolState if toolData or… #1181
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.
… toolData.data do not exist
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
It prevents errors if removeToolState is called when no toolData is present.
What is the current behavior? (You can also link to an open issue here)
An error will be thrown when toolData.data is accessed, but toolData is undefined.
What is the new behavior (if this is a feature change)?
It will exit early, avoiding the issue.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: