c5546f4a39
* add skeleton for global_search plugin * base implementation of the server-side service * add utils tests * add server-side mocks * move take_in_array to common folder * implements base of client-side plugin * add tests for server-side service * fix server plugin tests * implement `navigateToUrl` core API * extract processResults for the client-side * fetch server results from the client side * factorize process_results * fix plugin start params * move things around * move all server types to single file * fix types imports * add basic FTR tests * add client-side service tests * add tests for addNavigate * add getDefaultPreference & tests * use optional for RequestHandlerContext * add registerRoutes test * add base test for context * resolve TODO * common nits/doc * common nits/doc on public * update CODEOWNERS * add import for declare statement * add license check on the server-side * add license check on the client-side * eslint * address some review comments * use properly typed errors for obs * add integration tests for the find endpoint * fix unit tests * use licensing start contract * translate the error message * fix eslint rule for test_utils * fix test_utils imports * remove NavigableGlobalSearchResult, use `application.navigateToUrl` instead. * use coreProvider plugin in FTR tests * nits * fix service start params * fix service start params, bis * I really need to fix this typecheck oom error * add README, update missing jsdoc * nits on doc |
||
|---|---|---|
| .. | ||
| common | ||
| public | ||
| server | ||
| constants.ts | ||
| kibana.json | ||
| README.md | ||
Kibana Reporting
An awesome Kibana reporting plugin
Development
Assuming you've checked out x-plugins next to kibana...
- Run
yarn kbn bootstrap - Run
yarn startto watch for and sync files on change - Open a new terminal to run Kibana - use
yarn startto launch it in dev mode- Kibana will automatically restart as files are synced
- If you need debugging output, run
DEBUG=reporting yarn startinstead
If you have installed this somewhere other than via x-plugins, and next to the kibana repo, you'll need to change the pathToKibana setting in gulpfile.js
Conventions
This plugins adopts some conventions in addition to or in place of conventions in Kibana (at the time of the plugin's creation):
Folder structure
export_types/ (contains public and server aspects of the different export types)
printable_pdf/
public/
server/
csv/
public/
server/
public/ (shared public code for all export types)
server/ (shared server code for all export types)
This folder structure treats the different export_types like Plugins, with their public/server code being separate in a folder.