-
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
[Search] Introduce search navigation plugin #200314
Changes from 6 commits
91c2098
b991bf1
3671ee0
f5ac08c
7c43a4c
e53350c
deb3dfe
7d05b1f
b6835d7
5087471
f7c2b27
e5f792a
371c4a7
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 |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Search Navigation | ||
|
||
The Search Navigation plugin is used to handle navigation for search solution plugins across both stack and serverless. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
/* | ||
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one | ||
* or more contributor license agreements. Licensed under the Elastic License | ||
* 2.0; you may not use this file except in compliance with the Elastic License | ||
* 2.0. | ||
*/ | ||
|
||
export const PLUGIN_ID = 'searchNavigation'; | ||
export const PLUGIN_NAME = 'searchNavigation'; |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
/* | ||
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one | ||
* or more contributor license agreements. Licensed under the Elastic License | ||
* 2.0; you may not use this file except in compliance with the Elastic License | ||
* 2.0. | ||
*/ | ||
|
||
module.exports = { | ||
preset: '@kbn/test', | ||
rootDir: '../../../..', | ||
roots: ['<rootDir>/x-pack/plugins/search_solution/search_navigation'], | ||
coverageDirectory: | ||
'<rootDir>/target/kibana-coverage/jest/x-pack/plugins/search_solution/search_navigation', | ||
coverageReporters: ['text', 'html'], | ||
collectCoverageFrom: [ | ||
'<rootDir>/x-pack/plugins/search_solution/search_navigation/{public,server}/**/*.{ts,tsx}', | ||
], | ||
}; |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
{ | ||
"type": "plugin", | ||
"id": "@kbn/search-navigation", | ||
"owner": "@elastic/search-kibana", | ||
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. We need to define a
Is this a follow-up of this discussion? 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.
Not exactly, this is more architectural work to make it easier for Search team to develop plugins with UIs that are shared between stack and Serverless Elasticsearch. But this PR does enable us to remove search playground from 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. @gsoldevila I added the |
||
"plugin": { | ||
"id": "searchNavigation", | ||
"server": false, | ||
"browser": true, | ||
"configPath": [ | ||
"xpack", | ||
"searchNavigation" | ||
], | ||
"requiredPlugins": [], | ||
"optionalPlugins": [ | ||
"serverless" | ||
], | ||
"requiredBundles": [] | ||
} | ||
} |
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.
Should we name this
search
instead ofsearch_solution
and keep name consistency with the one for packages?x-pack/packages/search
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.
so I was using
observability_solution
&observability_solution
as the examples for this andsearch
seemed too generic.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.
Thats fair.
security
is the other one. I dont mind either but would be good we keep consistency and rename the other folder in packages (whilst theres only one package)