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
feat: implement secondary navigation for datasets #9982
feat: implement secondary navigation for datasets #9982
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9982 +/- ##
==========================================
- Coverage 71.38% 70.42% -0.97%
==========================================
Files 585 586 +1
Lines 30949 31072 +123
Branches 3261 3281 +20
==========================================
- Hits 22094 21883 -211
- Misses 8746 9078 +332
- Partials 109 111 +2
Continue to review full report at Codecov.
|
4dd33f7
to
21cbf89
Compare
text-transform: uppercase; | ||
font-weight: 500; | ||
font-size: @font-size-s; | ||
background-color: #20a7c9; |
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.
Can we make the blue "+DATASET" button @brand-primary
for the time being.
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.
just a couple comments re: translation. otherwise looks good
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.
Just one thought on color variables :)
font-size: @font-size-s; | ||
padding: 8px; | ||
margin: 8px; | ||
color: #3d3d3d; |
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.
Should this be a color variable?
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.
seconded: if there is any chance these colors will be reused it should be moved into a variable
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.
In cases of grays like this, there should be one pretty close to what you need... and we can adjust the global variable(s) to move closer to the new design as needed. Ping me if you want to discuss.
} | ||
li.active > a, | ||
li > a:hover { | ||
background: #eceef2; |
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.
Same question - should this be a variable?
@@ -34,6 +34,8 @@ | |||
@gray-bg: #f5f5f5; | |||
@gray-heading: #a3a3a3; | |||
@menu-hover: #f2f3f5; | |||
@gray-light-hover: #eceef2; | |||
@gray-drak-heading: #3d3d3d; |
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.
typo? should we just reuse one of the greys above?
border-radius: 4px; | ||
} | ||
} | ||
} |
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.
Hmm, should we move these to styled components or are we ok with living in a world with a mix of less + css-in-js?
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.
@ktmud good suggestion. I think moving to these to styled components will be cleaner. I will move css to the component.
* under the License. | ||
*/ | ||
import React from 'react'; | ||
import { Button, Nav, Navbar, MenuItem } from 'react-bootstrap'; |
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.
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.
To me migrating away from bootstrap is an important decision with intricate considerations that are outside the scope of this PR. We should start a [DISCUSS]
thread on the mailing list on this topic.
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.
There were some discussion when SIP-34 was closed and I thought the general consensus was we wanted to at least move away from Bootstrap 3?
If we are to implement new UI components for the new design, it'd be the best to start clean and reduce dependencies on Bootstrap as much as possible, especially if the component doesn't need to reuse much styling from Bootstrap anyway.
SUMMARY
This PR is part of new UX/UI design for Superset, see SIP-34. It updates "Sources" navigation menu to new secondary navigation component below the main navigation. New navigation bar is behind feature
LIST_VIEWS_NEW_UI
andENABLE_REACT_CRUD_VIEWS
. The reset of the redesign is still working in process.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
After:
TEST PLAN
ADDITIONAL INFORMATION