-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Unified rules] Hide stack rules from global search #260088
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
Changes from all commits
70c4929
e1e1cf1
a0dee87
43a11cb
652a5cf
444f235
0cf4649
c80d47c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,6 +15,7 @@ import type { | |
| CoreStart, | ||
| ChromeBreadcrumb, | ||
| CoreTheme, | ||
| AppDeepLinkLocations, | ||
| } from '@kbn/core/public'; | ||
| import type { LocatorPublic } from '@kbn/share-plugin/common'; | ||
| import type { CardsNavigationComponentProps } from '@kbn/management-cards-navigation'; | ||
|
|
@@ -110,6 +111,7 @@ export interface CreateManagementItemArgs { | |
| icon?: string; // URL to image file; fallback if no `euiIconType` | ||
| hideFromSidebar?: boolean; | ||
| hideFromGlobalSearch?: boolean; // Hide from global search results | ||
| visibleIn?: AppDeepLinkLocations[]; // Controls deep link visibility; takes precedence over hideFromGlobalSearch | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a reason t have both hideFromGlobalSearch and visibleIn? Could
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hideFromGlobalSearch is being used in a couple of other places. This is a last minute change as part of the unified rules effort next week, trying to get approvals for its removal may delay us. I also didn't want to nuke a use case I'm not aware of. visibleIn is a newer toggle used elsewhere in Kibana for deep link visibility management. I agree it's vague, but I didn't want to break away from convention in one place and have a discrepancy with how we manage visibility
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I just wanted to verify my understanding, any cleanup could happen later.
Looks like its used in the core app interface, good reason to reuse it. |
||
| capabilitiesId?: string; // overrides app id | ||
| redirectFrom?: string; // redirects from an old app id to the current app id | ||
| } | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -351,6 +351,7 @@ export class Plugin | |
| id: PLUGIN_ID, | ||
| title: featureTitle, | ||
| order: 1, | ||
| visibleIn: [], | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. added visibleIn here to avoid changing the intentions behind hideFromGlobalSearch filter in management plugin. We still need the app in deep links to retain sidenav appearance |
||
| async mount(params: ManagementAppMountParams) { | ||
| const [coreStart] = (await core.getStartServices()) as [CoreStart, PluginsStart, unknown]; | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.