Fix failure of revealing webview with viewColumn which does not exist #87832
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.
Currently,
create a webview
andreveal a webview
's behavior is not consistent, when aviewColumn
option is provided, but that column(group) does not exist:SIDE_GROUP
will open the webview on the active group's sideSIDE_GROUP
will do nothing (revealed on the webview's current group)The root cause of such inconsistency is in that
createWebview
forward the viewColumn(group) information toeditorService.openEditor
, which will be handled byeditorService.findTargetGroup
.However,
revealWebview
gets hands dirty to find the target group by itself, and some important logic is missing, e.g. handling ofSIDE_GROUP
. So when passingviewColumn
to be 1 (start from 0) when there's only 1 column, it will be revealed to column 0 instead of 1.This PR makes
editorService.findTargetGroup
public, and foward the group number to it to reuse its logic, and keep the behavior ofrevealing
andcreating
consistent.This PR fixes #71608.