Do not ScopeObserver#scopeReferenceCounts when outlet is called before controller is connected #771
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.
Fixes #763
The problem occurs when Outlet is accessed before controller has been connected by Stimulus and somebody tries to disconnect such controller later.
in such case
ScopeObserver#elementMatchedValue
is called 2 times sothis.scopeReferenceCounts
is eq 2.and during
ScopeObserver#elementUnmatchedValue
this counterthis.scopeReferenceCounts
remains >= 1 soscopeDisconnected(value)
is not called