-
Notifications
You must be signed in to change notification settings - Fork 18
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
33 - Create the navigation elements of the design system #54
33 - Create the navigation elements of the design system #54
Conversation
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.
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.
Found a typo so I'm pulling this out of QA. Still reviewing.
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.
Overall, this is looking great. I found a couple more little things.
defaultActiveKey: string | ||
} | ||
|
||
function Tabs({ defaultActiveKey, children }: PropsWithChildren<TabsProps>) { |
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.
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.
@MellyGray yes, you're right. I hope you don't mind but I did git rebase develop
on this PR and then force pushed it. The Props heading is there now:
4b03d80
to
7ce257a
Compare
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.
All set now after a couple typo fixes and rebasing. Tests are passing. Off to QA.
I'm not sure what I should be seeing, verifying. I see a navbar item in the left hand links column. I open the docs for it and see model navbar header components: links, drop down list, but I do not see tabs? |
When you open storybook there should be 3 elements for the navigation: the Navbar, the Tabs and the Breadcrumbs |
@MellyGray Thanks! I think it was the same -b issue. I wasn't seeing the latest? Anyway, I see them now. |
@MellyGray There is a merge conflict with the pr. Can you take a look? |
@kcondon I fixed the conflicts now |
…ements-of-the-design-system 33 - Create the navigation elements of the design system
What this PR does / why we need it:
This PR adds the navigation elements of the design system. This is the Navbar.tsx, Breadcrumb.tsx and Tabs.tsx components.
Which issue(s) this PR closes:
Special notes for your reviewer:
I added the 3 navigation elements as described in the Design System Analysis following Bootstrap 5 styles. For the Navbar element since it was already developed I just did a refactor to improve readability.
Suggestions on how to test this:
npm run storybook
You can check in the Storybook the Breadcrumbs, Tabs and Navigation elements
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
None
Is there a release notes update needed for this change?:
Added navigation elements of the design system
Additional documentation:
Design System Analysis doc