-
Notifications
You must be signed in to change notification settings - Fork 579
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
Sharable ports UI redesign #13215
Comments
coder-labeler
bot
added
design
Request for more beauty
s3
Bugs that confuse, annoy, or are purely cosmetic
site
Area: frontend dashboard
labels
May 9, 2024
matifali
added
feature
Something we don't have yet
and removed
s3
Bugs that confuse, annoy, or are purely cosmetic
feature
Something we don't have yet
labels
May 9, 2024
Taking resources off of this so we can stay focused on RBAC and Workspace Activity this sprint. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally raised by @pauliuspetk here:
#11486 (comment)
The sharable ports UI is a little overly complex since we added protocol control. There are several overly implicit flows and a few duplicate methods of achieving the same result. We've had to work directly with customers already to explain the feature's usage.
I agree with @pauliuspetk we should consolidate into a single table; this was actually part of some of our original mockups. All controls would be in-line with their respective port.
Here, all listening ports would default to the hidden "Owner" and HTTP. Shared ports would be pinned to the top of the list and remain visible even if the listening port goes quiet.
The text was updated successfully, but these errors were encountered: