Skip to content

Conversation

LieutenantRoger
Copy link
Contributor

No description provided.

@@ -22,7 +22,7 @@ const SubNav = ({
const to = _.isEmpty(level3.link) ? level3.href : level3.link
return (
<Link
className={cn(styles.secondaryNavItem, level3.id === activeChildId && styles.secondaryNavItemOpen)}
className={cn(styles.secondaryNavItem, level3.id === activeChildId && styles.secondaryNavItemOpen, level3.title === 'All Challenges' && styles.allChallengeClickable)}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LieutenantRoger This not a valid solution, because this is hardcoded if we change the menu to any other sentence this fix will stop working.

@@ -72,6 +72,10 @@
@include Roboto-Bold;
@include not-clickable;
}
&.allChallengeClickable {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also just add CSS class to specific menu name not valid.

Copy link
Collaborator

@luizrrodrigues luizrrodrigues left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check comments in code.

Also solution need be done in logic of navigation, try check this section:
src/components/TopNav/index.js line: 435

@LieutenantRoger
Copy link
Contributor Author

LieutenantRoger commented Jan 18, 2020

try check this section: src/components/TopNav/index.js line: 435

This method can't detect the change of the query parameter in the url, this is the reason causing this bug.

Please advise otherwise way, maybe passing the query parameter into the TopNav component as well ?

Or we can just allow user to re-click/re-enter the same level3 menu item, it doesn't have negative user experience as well IMO.

@luizrrodrigues
Copy link
Collaborator

I'll get confirmation about this and back to you.

@luizrrodrigues
Copy link
Collaborator

@LieutenantRoger Please follow this way:

Please advise otherwise way, maybe passing the query parameter into the TopNav component as well ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants