-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Navigation Component: Stop Updating the Active Menu on Active Item Change #25608
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
Size Change: +1.38 kB (0%) Total Size: 1.17 MB
ℹ️ View Unchanged
|
david-szabo97
approved these changes
Sep 24, 2020
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.
LGTM! 👍 🚢
5f1e0ab
to
b53543e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[Feature] Navigation Component
A navigational waterfall component for hierarchy of items.
[Type] Bug
An existing feature does not function as intended
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Navigation
components withactiveMenu
controlled externally butactiveMenu
internally, can't activate items in nested menus.This is caused by the
useEffect
that attempt to sync theactiveMenu
between internal and external state, being triggered onactiveItem
change.If the external
activeMenu
is not provided, it defaults toROOT_MENU
and never changes.So, when we activate an item in a nested menu, we trigger that
useEffect
, which checks if the internalmenu
is not in sync with the externalactiveMenu
, and updates the former with the latter.Since the external
activeMenu
is alwaysROOT_MENU
, every time we activate an item in a nested menu, we accidentally activateROOT_MENU
.The fix
Just remove
activeItem
from thatuseEffect
dependencies.This way, the active menu will only be syncd when the external
activeMenu
changes, which means that it's externally controlled, which is the only case we need to sync it.How has this been tested?
npm run storybook:dev
I've set the base for this PR on
update/navigation-component-stories
(#25572), which is where I've noticed this issue, to make it easier to test.Once approved, I'll merge this on master.
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: