-
Notifications
You must be signed in to change notification settings - Fork 92
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
Make output channel names consistent #5833
Make output channel names consistent #5833
Conversation
E2E Tests 🚀 ? |
Love it! Dhruvi and I synced up briefly, while we'd love to maybe someday have nice grouping or other organization of the Positron components (such as consoles together, kernels, or language runtimes, etc), making the naming nice and consistent is a great first pass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is working great for me, and the naming updates are a HUGE improvement:
I agree with @jthomasmock that eventually we would like to have more organization here so it is easier for users to find the relevant channels as tracked in #5063, but this PR is a big step in the right direction in terms of clarity and consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to go once everything is green! ✅
Description
Addresses #1707
@:output
We've received feedback that the output channel list is confusing and not easy to parse. A lot of the channel names are prefixed with "Positron" which is redundant. The formatting of the names for the language channels is not consistent and adds friction to the UX when scanning the list.
The proposed change here does some tidying 🧹 of the names to improve the UX:
Screenshots