-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
style: improve "Datasource & Chart Type" <Label>s #10971
Conversation
Overall great improvements! But I'm a little worried that the interaction with DatasourceControl may have become a little more confusing. The gray pill looks the same like the clickable labels in other controls (Viz Type and Time Range) but is not actually clickable. Using the cog icon for a dropdown menu also seems a little anti-pattern. What do you think of keeping it as a button/label with a dropdown menu and limiting this PR to just changing the style? |
I totally agree about the dataset label, maybe the label should have a caret and be a dropdown button, but it seemed harder than it should be to do that. About the 3 vertical dots? |
may I humbly ask UI changes can somehow go thru Product and Design? 🙏 I was planning to work on those labels with Design next sprint. we received some feedback from multiple users ... @mistercrunch |
@junlinc I tagged About the motives, I think the recently tweaked default is way too dark and "pops" way too much in this current state. The previous "white on a lighter gray" had usability issues, so I figure I'd go "black on light-gray with a light border" and it looks much better to me than before. More generally, I'm not sure if the label-with-popover pattern for controls is the right approach. I'd be curious to see how it would look if we'd redesign it from scratch. Open to suggestion & tweaks! |
284a136
to
2398e30
Compare
Codecov Report
@@ Coverage Diff @@
## master #10971 +/- ##
==========================================
- Coverage 65.79% 61.12% -4.68%
==========================================
Files 816 816
Lines 38422 38419 -3
Branches 3621 3621
==========================================
- Hits 25280 23483 -1797
- Misses 13034 14750 +1716
- Partials 108 186 +78
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There's another PR open where all the icons are moving over from the design system to the codebase. I'm trying to keep the names matching between Figma and the code, so there's a bit of overlap/misalignment with what's in this PR. In this PR, you're adding a few icons, which are also in the other one, but with different names. Would it be OK to ask for rebasing/renaming when that other PR slides in, lest they both merge and we have duplicates? Mapping (names): FWIW, the emerging standard for naming seems to be underscores in filenames (partly thanks to Figma) and dashes in the name values, as you have it. |
I also took some of your ideas and melded them into #11034 which uses your inverted/lightened default color, but treats the stroke/border idea differently, applying it to labels of any color, but only when they have an That said, this is probably a stopgap solution in the longer term, and many of these clickable labels should be replaced by Buttons, Dropdowns, etc. |
closing in favor of #11034 |
Oh, reopening for things not covered in #11034 |
34cfb3a
to
d8d7b08
Compare
@rusackas - rebased! |
d8d7b08
to
86c43f9
Compare
e759ac8
to
91d85f5
Compare
91d85f5
to
dcbffd2
Compare
* style: improve default <Label> * fix name-shifting icon * adding some styles to remove the inner drop shadow from the 'more' button Co-authored-by: Evan Rusackas <[email protected]>
after
before
storybook