[Solution Side Nav] Remove PanelContentProvider & support optional title in nav node#218156
Conversation
f823a8e to
9a88105
Compare
|
Pinging @elastic/appex-sharedux (Team:SharedUX) |
| path: 'group1.item1', | ||
| }, | ||
| ], | ||
| ] as ChromeProjectNavigationNode[], |
There was a problem hiding this comment.
I'm not entirely sure why this was necessary 🤔
71710bf to
f471af8
Compare
| { | ||
| id: 'footer-section5', | ||
| title: 'Parent item, closed', | ||
| id: 'example_project_footer', |
There was a problem hiding this comment.
footer should have a single group of sub-items, with no title for that group
f471af8 to
3cda9eb
Compare
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
History
|
|
Starting backport for target branches: 8.x https://github.com/elastic/kibana/actions/runs/14472802881 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…tle in nav node (elastic#218156) Epic: elastic/kibana-team#1439 Needed for elastic#218050 (adjustments to types for `title` field in `ChromeProjectNavigationNode`) ## Summary 1. `PanelContentProvider` was used for security solution, but is no longer used. This removes it to simplify the interfaces for panel . 2. Allow title of `navGroup` to be optional. This allows the correct design for nav items in the footer, which are child-items of a nav group with no title ## Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios (cherry picked from commit b9c2b57)
…nal title in nav node (#218156) (#218330) # Backport This will backport the following commits from `main` to `8.x`: - [[Solution Side Nav] Remove PanelContentProvider & support optional title in nav node (#218156)](#218156) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-15T15:04:01Z","message":"[Solution Side Nav] Remove PanelContentProvider & support optional title in nav node (#218156)\n\nEpic: https://github.com/elastic/kibana-team/issues/1439\nNeeded for #218050 (adjustments to\ntypes for `title` field in `ChromeProjectNavigationNode`)\n\n## Summary\n\n1. `PanelContentProvider` was used for security solution, but is no\nlonger used. This removes it to simplify the interfaces for panel .\n2. Allow title of `navGroup` to be optional. This allows the correct\ndesign for nav items in the footer, which are child-items of a nav group\nwith no title\n\n## Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"b9c2b57c23d1d74d4fef025d64b820216ddce272","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:version","v9.1.0","v8.19.0"],"title":"[Solution Side Nav] Remove PanelContentProvider & support optional title in nav node","number":218156,"url":"https://github.com/elastic/kibana/pull/218156","mergeCommit":{"message":"[Solution Side Nav] Remove PanelContentProvider & support optional title in nav node (#218156)\n\nEpic: https://github.com/elastic/kibana-team/issues/1439\nNeeded for #218050 (adjustments to\ntypes for `title` field in `ChromeProjectNavigationNode`)\n\n## Summary\n\n1. `PanelContentProvider` was used for security solution, but is no\nlonger used. This removes it to simplify the interfaces for panel .\n2. Allow title of `navGroup` to be optional. This allows the correct\ndesign for nav items in the footer, which are child-items of a nav group\nwith no title\n\n## Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"b9c2b57c23d1d74d4fef025d64b820216ddce272"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/218156","number":218156,"mergeCommit":{"message":"[Solution Side Nav] Remove PanelContentProvider & support optional title in nav node (#218156)\n\nEpic: https://github.com/elastic/kibana-team/issues/1439\nNeeded for #218050 (adjustments to\ntypes for `title` field in `ChromeProjectNavigationNode`)\n\n## Summary\n\n1. `PanelContentProvider` was used for security solution, but is no\nlonger used. This removes it to simplify the interfaces for panel .\n2. Allow title of `navGroup` to be optional. This allows the correct\ndesign for nav items in the footer, which are child-items of a nav group\nwith no title\n\n## Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"b9c2b57c23d1d74d4fef025d64b820216ddce272"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
## Summary Epic: elastic/kibana-team#1439 ~Depends on #218156 Addresses footer issues and a few content issues https://github.com/user-attachments/assets/07063aa7-8a49-4cb5-9fd2-a6e1cbd674b7 1. Footer item texts should not be bold 2. We should have the spacing of regular nav sub-items in the footer Other fixes: 1. Fix text casing in "Machine Learning" (Note: [other casing issues exist](#217352)) 2. Remove `recentlyAccessed` sections ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary Epic: elastic/kibana-team#1439 Depends on #218513 ### List of changes 1. Match header text style with the main panel 2. Match spacing between items with the main panel 3. Show horizontal line between groups in the panel - This restores a custom error that was in the code prior to #218156, but adds better handling and tests to the error 5. Fix position of accordion group arrows in the secondary panel (viewable only from Storybook) 6. isOpen is not really needed and can be cleaned up - (see https://github.com/elastic/kibana/pull/217708/files#diff-9e95eb3e4be14fb61caca86b48be4f03ca63393eeeadcd0b36f7371958a7e5e1L55) 7. (not panel-related) remove the on-hover and on-focus underline from nav items ### Checklist from Kate: - [x] text font-weight of solution title in main panel - [x] text font-weight of secondary panel link content - [x] zero space between items - [x] use ~~12px~~ nice-looking margin from the link to the edge of the panel - [x] ensure the divider reaches to the edge of the panel - [x] increase space from panel header to the items - [x] ensure the width of both panels is 248px - [x] secondary panel header should vertically align with the below nav items - [x] (not panel-related) font color and icon color of selected items should be "primary" blue ### Screenshots **Security Solution Serverless** https://github.com/user-attachments/assets/83ca1c25-f44a-4270-96a8-e28e7b6d7041 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary Epic: elastic/kibana-team#1439 ~Depends on elastic#218156 Addresses footer issues and a few content issues https://github.com/user-attachments/assets/07063aa7-8a49-4cb5-9fd2-a6e1cbd674b7 1. Footer item texts should not be bold 2. We should have the spacing of regular nav sub-items in the footer Other fixes: 1. Fix text casing in "Machine Learning" (Note: [other casing issues exist](elastic#217352)) 2. Remove `recentlyAccessed` sections ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary Epic: elastic/kibana-team#1439 Depends on elastic#218513 ### List of changes 1. Match header text style with the main panel 2. Match spacing between items with the main panel 3. Show horizontal line between groups in the panel - This restores a custom error that was in the code prior to elastic#218156, but adds better handling and tests to the error 5. Fix position of accordion group arrows in the secondary panel (viewable only from Storybook) 6. isOpen is not really needed and can be cleaned up - (see https://github.com/elastic/kibana/pull/217708/files#diff-9e95eb3e4be14fb61caca86b48be4f03ca63393eeeadcd0b36f7371958a7e5e1L55) 7. (not panel-related) remove the on-hover and on-focus underline from nav items ### Checklist from Kate: - [x] text font-weight of solution title in main panel - [x] text font-weight of secondary panel link content - [x] zero space between items - [x] use ~~12px~~ nice-looking margin from the link to the edge of the panel - [x] ensure the divider reaches to the edge of the panel - [x] increase space from panel header to the items - [x] ensure the width of both panels is 248px - [x] secondary panel header should vertically align with the below nav items - [x] (not panel-related) font color and icon color of selected items should be "primary" blue ### Screenshots **Security Solution Serverless** https://github.com/user-attachments/assets/83ca1c25-f44a-4270-96a8-e28e7b6d7041 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary Epic: elastic/kibana-team#1439 ~Depends on elastic#218156 Addresses footer issues and a few content issues https://github.com/user-attachments/assets/07063aa7-8a49-4cb5-9fd2-a6e1cbd674b7 1. Footer item texts should not be bold 2. We should have the spacing of regular nav sub-items in the footer Other fixes: 1. Fix text casing in "Machine Learning" (Note: [other casing issues exist](elastic#217352)) 2. Remove `recentlyAccessed` sections ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
## Summary Epic: elastic/kibana-team#1439 Depends on elastic#218513 ### List of changes 1. Match header text style with the main panel 2. Match spacing between items with the main panel 3. Show horizontal line between groups in the panel - This restores a custom error that was in the code prior to elastic#218156, but adds better handling and tests to the error 5. Fix position of accordion group arrows in the secondary panel (viewable only from Storybook) 6. isOpen is not really needed and can be cleaned up - (see https://github.com/elastic/kibana/pull/217708/files#diff-9e95eb3e4be14fb61caca86b48be4f03ca63393eeeadcd0b36f7371958a7e5e1L55) 7. (not panel-related) remove the on-hover and on-focus underline from nav items ### Checklist from Kate: - [x] text font-weight of solution title in main panel - [x] text font-weight of secondary panel link content - [x] zero space between items - [x] use ~~12px~~ nice-looking margin from the link to the edge of the panel - [x] ensure the divider reaches to the edge of the panel - [x] increase space from panel header to the items - [x] ensure the width of both panels is 248px - [x] secondary panel header should vertically align with the below nav items - [x] (not panel-related) font color and icon color of selected items should be "primary" blue ### Screenshots **Security Solution Serverless** https://github.com/user-attachments/assets/83ca1c25-f44a-4270-96a8-e28e7b6d7041 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Epic: https://github.com/elastic/kibana-team/issues/1439
Needed for #218050 (adjustments to types for
titlefield inChromeProjectNavigationNode)Summary
PanelContentProviderwas used for security solution, but is no longer used. This removes it to simplify the interfaces for panel .navGroupto be optional. This allows the correct design for nav items in the footer, which are child-items of a nav group with no titleProgress towards fixing footer issues
The look and feel of nav items in the footer was wrong. Now that
navGrouptitles are optional, we can make footer navigation items appear more like the intended design. Run theyarn storybook shared_uxand view theChrome Navigationpage for the proper way footer nav items should look.To achieve this fix within Solutions, teams will need to update their navigation structure and move the top-level footer items into a single
navGroup.Example code fix
File:
x-pack/solutions/observability/plugins/observability/public/navigation_tree.tsChecklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.