fix: don't throw unhandled errors in TabstopManager when EditSession becomes undefined
#5193
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.
Issue #, if available:
Description of changes:
editor.setSession
seems to account for the possibility ofsession
being falsy (e.g.:undefined
,null
). At the end of this method, theeditor
signals there was a change in thesession
session
is changed,TabstopManager
runs itsdetach
method. This method was eventually expecting to use thesession
instance to remove markers, which is not possible when it isundefined
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.