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

Move attached containers to dev containers #1963

Closed
dbaeumer opened this issue Dec 4, 2019 · 13 comments
Closed

Move attached containers to dev containers #1963

dbaeumer opened this issue Dec 4, 2019 · 13 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug polish verified Verification succeeded
Milestone

Comments

@dbaeumer
Copy link
Member

dbaeumer commented Dec 4, 2019

Testing #1938

The container is still shown as attached although I closed the VS Code instance that was attached to it.

capture

@alexr00
Copy link
Member

alexr00 commented Dec 4, 2019

"Attached Containers" are containers that you can attach to or have attached to. This looks correct since it doesn't have the green currently-connected-with-this-window icon.

@alexr00 alexr00 added the *as-designed Described behavior is as designed label Dec 4, 2019
@vscodebot
Copy link

vscodebot bot commented Dec 4, 2019

The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Dec 4, 2019
@alexr00 alexr00 closed this as completed Dec 4, 2019
@dbaeumer
Copy link
Member Author

dbaeumer commented Dec 4, 2019

I have to say that the wording is pretty misleading. For me "Attached Containers" are containers I am attached to :-) I would never look for a green circle

@dbaeumer
Copy link
Member Author

dbaeumer commented Dec 4, 2019

And actually it is not true. This container I have been attached to and now shows up as Other Containers.

capture

@dbaeumer
Copy link
Member Author

dbaeumer commented Dec 4, 2019

capture

@alexr00
Copy link
Member

alexr00 commented Dec 4, 2019

We only move the container from Other to Attached once you've opened a folder.

@dbaeumer
Copy link
Member Author

dbaeumer commented Dec 4, 2019

I would have never guessed this :-).

I am also not convinced that this is something others will understand easily. Is this not something that is more a Favorite or Last recently used concept. That I would understand :-)

@alexr00
Copy link
Member

alexr00 commented Dec 4, 2019

That's actually what we're using to tell whether a container is Attached or Other. We use the recently opened folders and populate much of the view from there.
@chrmarti what do you think of changing "Attached" to "Recently Attached"?

@chrmarti
Copy link
Contributor

chrmarti commented Dec 5, 2019

The currently attached container would also show under "Recently Attached"? 🤔

@alexr00
Copy link
Member

alexr00 commented Dec 5, 2019

Yes, it would just be a string change in the tree.

@chrmarti
Copy link
Contributor

chrmarti commented Dec 5, 2019

The distinction between Attached Containers and Dev Containers is becoming more artificial as we extend the attach case. Maybe we could have them all under Dev Containers.

@dbaeumer
Copy link
Member Author

dbaeumer commented Dec 6, 2019

That makes sense to me. We could also think about removing Dev and simply call them containers. I know that I am developing :-)

@alexr00 alexr00 changed the title Container still shown as attached although I closed the VS Code instance. Move attached containers to dev containers Dec 6, 2019
@alexr00 alexr00 added bug Issue identified by VS Code Team member as probable bug polish and removed *as-designed Described behavior is as designed labels Dec 6, 2019
@alexr00 alexr00 added this to the December 2019 milestone Dec 6, 2019
@alexr00 alexr00 reopened this Dec 6, 2019
@alexr00 alexr00 closed this as completed Jan 21, 2020
@alexr00
Copy link
Member

alexr00 commented Jan 21, 2020

Attached containers now show under Dev containers. They do still have different actions since that is needed.

@dbaeumer dbaeumer added the verified Verification succeeded label Jan 29, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug polish verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants