| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
PatternFly-React preview: https://2268-pr-patternfly-react-patternfly.surge.sh |
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## master #2268 +/- ##
=========================================
Coverage ? 79.89%
=========================================
Files ? 669
Lines ? 8531
Branches ? 734
=========================================
Hits ? 6816
Misses ? 1362
Partials ? 353
Continue to review full report at Codecov.
|
Sorry, something went wrong.
|
PatternFly-React preview: https://patternfly-react-pr-2268.surge.sh |
Sorry, something went wrong.
| className?: string; | ||
| /** Section background color variant */ | ||
| variant?: 'default' | 'light' | 'dark' | 'darker' | PageSectionVariants | ||
| variant?: 'default' | 'light' | 'dark' | 'darker' | PageSectionVariants; |
There was a problem hiding this comment.
Why are we adding the enum to union here? I don't think it is needed.
Sorry, something went wrong.
There was a problem hiding this comment.
This came in from the TS conversion, which I followed for the type prop I added. Should I remove the enums and just leave the unions?
Edit: Talked with @redallen and I removed them. It's not really needed.
Sorry, something went wrong.
| /** Section background color variant */ | ||
| variant?: 'default' | 'light' | 'dark' | 'darker' | PageSectionVariants | ||
| variant?: 'default' | 'light' | 'dark' | 'darker'; | ||
| /** Section type variant */ |
There was a problem hiding this comment.
when should consumers use nav? should there be an example? maybe a little more descriptive comment?
Sorry, something went wrong.
There was a problem hiding this comment.
Agreed. There is no example in core. @srambach will be opening up an additional issue to add one.
Sorry, something went wrong.
|
Results look good to me 👍 |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What: Adding missing page main nav section
Refer to issue: #1742