kibana/x-pack/plugins/reporting
Tim Sullivan 40fa961d53
[Reporting] Remove unused priority field (#92552)
* [Reporting] Remove unused priority field

* fix test

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2021-03-01 10:41:08 -07:00
..
common [Reporting] Remove unused priority field (#92552) 2021-03-01 10:41:08 -07:00
public [Reporting] Remove unused priority field (#92552) 2021-03-01 10:41:08 -07:00
server [Reporting] Remove unused priority field (#92552) 2021-03-01 10:41:08 -07:00
jest.config.js Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
kibana.json [Reporting] Use spaceId from request in export generation (#76998) 2020-09-18 13:08:15 -07:00
README.md [Reporting] Move code out of Legacy (#67904) 2020-06-03 15:40:56 -07:00
tsconfig.json [Presentation Team] Migrate to Typescript Project References (#86019) 2021-01-31 08:37:58 -06:00

Kibana Reporting

An awesome Kibana reporting plugin

Development

Assuming you've checked out x-plugins next to kibana...

  • Run yarn kbn bootstrap
  • Run yarn start to watch for and sync files on change
  • Open a new terminal to run Kibana - use yarn start to launch it in dev mode
    • Kibana will automatically restart as files are synced
    • If you need debugging output, run DEBUG=reporting yarn start instead

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.