-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
NavigationItemOpenPanel: remove handling of landing page ("four squares" design) #210893
base: main
Are you sure you want to change the base?
NavigationItemOpenPanel: remove handling of landing page ("four squares" design) #210893
Conversation
90e6ab1
to
e072275
Compare
e072275
to
099e52f
Compare
Pinging @elastic/security-solution (Team: SecuritySolution) |
Pinging @elastic/appex-sharedux (Team:SharedUX) |
const isExpanded = selectedNode?.path === path; | ||
const isActive = hasLandingPage ? isActiveFromUrl(item.path, activeNodes) : isExpanded; |
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.
Previous code had a bug: isActiveFromUrl
was only called if the nav item had a landing page. This was broken for the parent nav item buttons that are remaining in this PR.
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
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.
Changes in x-pack/test_serverless/functional/services/ml
LGTM
@tsullivan The code looks good, but with these changes we lose access to the custom I am talking with our PM to see how we can handle that. |
x-pack/test/security_solution_cypress/cypress/e2e/explore/navigation/navigation.cy.ts
Outdated
Show resolved
Hide resolved
@semd Understood. If we need to add changes to the Security Solution navigation tree in this PR, let's make sure we do that. I will probably need your guidance on where to add the code. Would you be able to send me a PR to this branch after the PM decisions are made?
@semd This is planned only for the next minor release, so 9.1.0 |
@tsullivan Yes, I can do that. I think we should keep this PR on hold until then. I'll keep you updated. |
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.
obs-ux-management code change LGTM
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
….com:tsullivan/kibana into solution-nav/ignore-link-when-renderas-panel
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
History
cc @tsullivan |
Summary
Part of Epic: https://github.com/elastic/kibana-team/issues/1439
Requires: #212903
Changes:
EuiCollapsibleNavBeta
component.@emotion/css
to@emotion/react
for better developer experienceScreenshots
Before
After
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*
label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.