-
Notifications
You must be signed in to change notification settings - Fork 81
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
feat: create new dropdown menu #666
Conversation
const globalClickListener = useCallback((nativeEvent) => { | ||
// ignore click event happened inside the dropdown menu | ||
if (dropdownRef.current && dropdownRef.current.contains(nativeEvent.target)) | ||
return |
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.
I’d suggest changing eslint (in another ticket) to not allow this style of return without curly braces.
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.
I could not find the rule. Do you know which one it might be?
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.
Define `<Dropdown>` and update `<BalanceSelector` to use it. Removing nested menu code because it is not used with current navigation and while support was defined for the desktop menu it was not for mobile in addition to the styles being very off on the desktop. Future PRs will use <Dropdown> in the header too. This will eliminate 3 menu implementations.
2086633
to
7c1a92c
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.
LGTM other than Justin's comments for the future
Moved BalanceSelector to its own folder.
High Level Overview of Change
Define
<Dropdown>
and update<BalanceSelector>
to use it.Removing nested menu code because it is not used with current navigation and while support was defined for the desktop menu it was not for mobile in addition to the styles being very off on the desktop.
Future PRs will use in the header too. This will eliminate 3 menu implementations.
Context of Change
Related to #554 and a new header design.
Type of Change
TypeScript/Hooks Update
Before
After
Future Tasks
Use new component in the header