-
Notifications
You must be signed in to change notification settings - Fork 561
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
Fixed: Ensure Header component uses proper semantic header HTML tag #3533
Conversation
🦋 Changeset detectedLatest commit: 63b936a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Hi @joshblack, This is my PR. Please can you guide me if there is anything that I missed or any advice? Thanks |
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 great! Thanks for doing this 🥳
For the test failure, I think all that's left to do is update the snapshots for the header tests! You can do this by running the following command: npm test -- -u And then including the snapshots in a commit and pushing them up to this Pull Request. Hope that makes sense, let me know if you have any questions! |
Thank you @joshblack for your guidance 🤗. I have committed test snapshots now. Hopefully, it works now. |
@amarmanhala seems like just one final change, in the test file for it('renders a <div> and <a>', () => {
- expect(render(<Header />).type).toEqual('div')
+ expect(render(<Header />).type).toEqual('header')
expect(render(<Header.Link />).type).toEqual('a')
}) After that you should be good to go! 🥳 |
Thank you @joshblack for your guidance. |
Thanks so much for your contribution @amarmanhala! 🙌 🥳 |
Changed div tag to HTML semantic element for Header component
Issue #2870
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.