-
Notifications
You must be signed in to change notification settings - Fork 1
Multi-level Navbar Menu #123
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
Conversation
|
This looks good. Just a couple of extra things:
I'll review it formally after you get the tests created. |
88ca5c4 to
9f75851
Compare
VictoriaBeilsten-Edmands
left a comment
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 and you've handles accessibility well. Just a couple of minor points.
9f75851 to
dda2f86
Compare
|
@JamesDoingStuff @VictoriaBeilsten-Edmands Any update on this? |
|
I've just noticed that I accidentally committed a bunch of auto-formatting to the changelog, so I'll get rid of that now, but otherwise I think I've made all the suggested changes - just needs approval |
1b5e1e9 to
83c2d0d
Compare
cfe3555 to
1193ca2
Compare
1193ca2 to
3cbd5a6
Compare
akademy
left a comment
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.
LG
For #52
Couple of things worth mentioning:
fireEventwas too restrictive)NavMenuLinkto work with focus I had to use ref forwarding, and to support router links without duplicating code, it now uses theNavLink, but this meant adding ref forwarding toNavLinkas well, lest the console fill up with React warnings.