Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate view label #141402

Closed
bpasero opened this issue Jan 25, 2022 · 1 comment
Closed

Duplicate view label #141402

bpasero opened this issue Jan 25, 2022 · 1 comment
Assignees
Labels
*as-designed Described behavior is as designed workbench-views Workbench view issues

Comments

@bpasero
Copy link
Member

bpasero commented Jan 25, 2022

Testing #141357

image

In this case could we not show "Debug" instead, since we know the original container?

@sbatten sbatten added bug Issue identified by VS Code Team member as probable bug workbench-views Workbench view issues labels Jan 25, 2022
@sbatten sbatten modified the milestones: January 2022, February 2022 Jan 25, 2022
@sbatten
Copy link
Member

sbatten commented Feb 24, 2022

I misread this issue the first time through. I no longer believe this is a bug but by design. That doesn't mean we can't improve the naming mechanism of containers, but I don't think auto-naming this debug is what we want to do.

The identity of the container you have created has to be automatically determined since it is a custom container (not debug since debug cannot be moved as a unit). therefore if you were to move watch to a panel and then put variables in a separate panel, we currently call them watch and variables, but this suggestion would make duplicate panels called debug. We already have a feature request to allow renaming of containers and I think that is more likely to address this type of issue.

@sbatten sbatten closed this as completed Feb 24, 2022
@sbatten sbatten added *as-designed Described behavior is as designed and removed bug Issue identified by VS Code Team member as probable bug labels Feb 24, 2022
@sbatten sbatten removed this from the February 2022 milestone Feb 24, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed workbench-views Workbench view issues
Projects
None yet
Development

No branches or pull requests

2 participants