[SideNav] v1 NavTree Structure Clean-Up#241943
Merged
Dosant merged 49 commits intoelastic:mainfrom Nov 25, 2025
Merged
Conversation
Dosant
commented
Nov 5, 2025
| }); | ||
|
|
||
| export const navigationTree = ({ isAppRegistered }: ApplicationStart): NavigationTreeDefinition => { | ||
| function isAvailable<T>(appId: string, content: T): T[] { |
Contributor
Author
There was a problem hiding this comment.
no need for this check afaik because it should be handled by navlinks status.
Contributor
There was a problem hiding this comment.
I agree, I'd have to look through to git blame to see when this got added an what it was trying to address since nav link should have always handled this.
4812f31 to
a5caee3
Compare
PhilippeOberti
approved these changes
Nov 24, 2025
Contributor
PhilippeOberti
left a comment
There was a problem hiding this comment.
Approving to unblock the PR but I'm still a bit confused about why the Value report is not working
Ikuni17
approved these changes
Nov 25, 2025
Contributor
⏳ Build in-progress
Failed CI StepsTest Failures
History
|
umbopepato
pushed a commit
to umbopepato/kibana
that referenced
this pull request
Nov 25, 2025
## Summary Follow up to elastic#241114 This time we cleaning up everything related to the navigation trees structure that is no longer needed in new nav - [x] Platform @Dosant - [x] Search @Dosant (@TattdCodeMonkey to review) - [x] Oblt @justinkambic - [x] Security @ashokaditya Guidance: - Use TypeScript errors to see what needs to be cleaned up: - All V1 property no longer needed. Please Review. V1 branches no longer needed - V2 properties renamed: iconV2 -> icon; badgeTypeV2 -> badgeType - Body and Footer no longer need intermediate root nodes! The nav nodes should go directly under body: [/* nodes */ ], footer: [/* footer */] - @justinkambic, @ashokaditya, use search trees as an example. I cleaned it up. --------- Co-authored-by: Justin Kambic <jk@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ashokaditya <ashokaditya@elastic.co>
seanrathier
pushed a commit
to seanrathier/kibana
that referenced
this pull request
Nov 25, 2025
## Summary Follow up to elastic#241114 This time we cleaning up everything related to the navigation trees structure that is no longer needed in new nav - [x] Platform @Dosant - [x] Search @Dosant (@TattdCodeMonkey to review) - [x] Oblt @justinkambic - [x] Security @ashokaditya Guidance: - Use TypeScript errors to see what needs to be cleaned up: - All V1 property no longer needed. Please Review. V1 branches no longer needed - V2 properties renamed: iconV2 -> icon; badgeTypeV2 -> badgeType - Body and Footer no longer need intermediate root nodes! The nav nodes should go directly under body: [/* nodes */ ], footer: [/* footer */] - @justinkambic, @ashokaditya, use search trees as an example. I cleaned it up. --------- Co-authored-by: Justin Kambic <jk@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ashokaditya <ashokaditya@elastic.co>
eokoneyo
pushed a commit
to eokoneyo/kibana
that referenced
this pull request
Dec 2, 2025
## Summary Follow up to elastic#241114 This time we cleaning up everything related to the navigation trees structure that is no longer needed in new nav - [x] Platform @Dosant - [x] Search @Dosant (@TattdCodeMonkey to review) - [x] Oblt @justinkambic - [x] Security @ashokaditya Guidance: - Use TypeScript errors to see what needs to be cleaned up: - All V1 property no longer needed. Please Review. V1 branches no longer needed - V2 properties renamed: iconV2 -> icon; badgeTypeV2 -> badgeType - Body and Footer no longer need intermediate root nodes! The nav nodes should go directly under body: [/* nodes */ ], footer: [/* footer */] - @justinkambic, @ashokaditya, use search trees as an example. I cleaned it up. --------- Co-authored-by: Justin Kambic <jk@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ashokaditya <ashokaditya@elastic.co>
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
## Summary Follow up to elastic#241114 This time we cleaning up everything related to the navigation trees structure that is no longer needed in new nav - [x] Platform @Dosant - [x] Search @Dosant (@TattdCodeMonkey to review) - [x] Oblt @justinkambic - [x] Security @ashokaditya Guidance: - Use TypeScript errors to see what needs to be cleaned up: - All V1 property no longer needed. Please Review. V1 branches no longer needed - V2 properties renamed: iconV2 -> icon; badgeTypeV2 -> badgeType - Body and Footer no longer need intermediate root nodes! The nav nodes should go directly under body: [/* nodes */ ], footer: [/* footer */] - @justinkambic, @ashokaditya, use search trees as an example. I cleaned it up. --------- Co-authored-by: Justin Kambic <jk@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Ashokaditya <ashokaditya@elastic.co>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow up to #241114
This time we cleaning up everything related to the navigation trees structure that is no longer needed in new nav
Guidance: