fix!: have disposing be true from start of dispose #7891
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.
The basics
The details
Resolves
Fixes #7864
Proposed Changes
Makes it so
disposing
is set at the beginning of thedispose
anddisposeInternal
methods.Reason for Changes
This way we can check
isDeadOrDying
in the dynamic connection plugin to get around issues with the dynamic connection plugin (see the linked issue for more detail).Test Coverage
Updated incorrect tests.
Documentation
N/A
Additional Information
N/A
Breaking changes / To fix
The
disposing
property is now true from the start of the call todispose
on blocks. Whereas before, it would only be true after we had removed top blocks, change listeners, and done a few other actions. This means thatisDeadOrDying
returns true from the start of the call todispose
.We think its unlikely that anyone was depending on the "delay" in the change to this value. So there is likely no work you need to do here. If you run into problems with this change, please let us know.