-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add menu state context for convenience #1012
Conversation
andrewkfiedler
commented
Feb 20, 2025
- In some scenarios it's useful to have context available for menustate to avoid the need for passing it down through multiple components in props. This mostly helps nested menus, but can be useful in other areas as well.
build now |
Internal build has been started, your results will be available at build completion. |
Build FAILURE See the job results in legacy Jenkins UI or in Blue Ocean UI. |
Suspected Failure(s):
|
- In some scenarios it's useful to have context available for menustate to avoid the need for passing it down through multiple components in props. This mostly helps nested menus, but can be useful in other areas as well.
abb014a
to
65dea41
Compare
build now |
Internal build has been started, your results will be available at build completion. |
An updated dist branch has been created and pushed to origin. Remember to use "yarn install --force" if you want to pick up changes each time you make a change to this branch by committing. |
Build SUCCESS See the job results in legacy Jenkins UI or in Blue Ocean UI. |
You can no longer use: Instead, if the pr was merged you can now access these changes by using: Remember to use "yarn install --force" if you want to pick up changes to this version. |