You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2021. It is now read-only.
It's not uncommon for us to use custom navigation walkers to modify the structure or underlying output of a navigation menu to adhere to alternative FED methodologies (be it BEM, ITCSS, etc).
This sometimes results in navigation items not having the class names expected by the Responsive Navigation component. It would be trivial to add these class names to the options object (with the existing core classes as defaults to maintain backward compatibility).
Happy to provide a PR if there's a consensus that this would be a valuable addition. Thanks for considering it!
The text was updated successfully, but these errors were encountered:
It's not uncommon for us to use custom navigation walkers to modify the structure or underlying output of a navigation menu to adhere to alternative FED methodologies (be it BEM, ITCSS, etc)
It's not uncommon for us to use custom navigation walkers to modify the structure or underlying output of a navigation menu to adhere to alternative FED methodologies (be it BEM, ITCSS, etc).
This sometimes results in navigation items not having the class names expected by the Responsive Navigation component. It would be trivial to add these class names to the options object (with the existing core classes as defaults to maintain backward compatibility).
Happy to provide a PR if there's a consensus that this would be a valuable addition. Thanks for considering it!
The text was updated successfully, but these errors were encountered: