feat: allow webviews in secondary side bar for extensions #247899
+10
−0
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.
Add support for contributing views to the
secondarybar
locationSummary
This PR enables extensions to contribute view containers and views to the Secondary Side Bar (
secondarybar
) using the existingviewsContainers
andviews
contribution points.What this change does
"secondarybar"
as a valid location forviewsContainers
.ViewContainerLocation.AuxiliaryBar
.Before
Only
"activitybar"
and"panel"
were accepted locations for contributed view containers:Extensions could not target the Secondary Side Bar for contributed views.
After
Developers can now contribute view containers to the
secondarybar
:Views inside this container will be rendered in the Auxiliary Bar.
Motivation
Allowing extensions to render in the Secondary Side Bar makes it possible to separate content logically—for example, Explorer in the primary sidebar and a custom Assistant in the secondarybar—without UI conflicts.
This increases flexibility and helps support more complex UI workflows in advanced extension scenarios.