-
Notifications
You must be signed in to change notification settings - Fork 4
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: remove <d2l-navigation-button> #183
Conversation
import '@brightspace-ui/button/d2l-button-behavior.js'; | ||
import '@brightspace-ui/polymer-behaviors/d2l-focusable-behavior.js'; | ||
import '@brightspace-ui/polymer-behaviors/d2l-id.js'; | ||
import { highlightStyles } from './d2l-navigation-highlight-styles.js'; |
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.
This and polymer-behaviors
are still used by <d2l-navigation-link>
-- so close!
@@ -56,7 +55,6 @@ | |||
"stylelint": "^14" | |||
}, | |||
"dependencies": { | |||
"@brightspace-ui/button": "^6", |
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 like Consistent Eval still uses it? https://github.com/Brightspace/consistent-evaluation/blob/master/components/footer/consistent-evaluation-footer.js#L130-L139 |
Ugh, my GitHub search for |
I tried |
Alright, I can't find any other references other than the one mentioned in the PR description. |
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.
🎉 🎊 🥳
🎉 This PR is included in version 5.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
All usages of this have been replaced with either
<d2l-navigation-button-icon>
or<d2l-navigation-dropdown-button-*>
! 🎉There's one remaining usage in nova-persona-manager but that project is still on the Lit 1 version of navigation, which doesn't have any of the new components. They're aware, and I've created a draft PR that they can just apply when they do the migration.