Fix: Properly setting selection range when KCL editor is not mounted. #4960
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.
closes #4859
Issue
lastSelectionEvent
is not properly set in one of theset selection
workflows so when the KCL editor is mounted it will break.Implementation
In the
completeSelection
workflow which is the selection workflow when a constraint is applied I properly compute the new selection range for the AST mod. I pass this range to thesetLastSelectionEvent
which then highlights the code in codemirror.If the range cannot be computed I select the bottom of the file by default so we can always have some selection event.
Future notes
It would be nice to have a clearer workflow for selection throughout the system. We have artifact selections as well as editor selections and then multiple different selection visuals within each one.