[NP] Graph migration

x-pack/legacy/plugins/graph/index.ts

@@ -4,31 +4,19 @@
  * you may not use this file except in compliance with the Elastic License.
  */
 
-import { resolve } from 'path';
 import { i18n } from '@kbn/i18n';
 
 // @ts-ignore
 import migrations from './migrations';
 import mappings from './mappings.json';
 import { LegacyPluginInitializer } from '../../../../src/legacy/plugin_discovery/types';
-import { DEFAULT_APP_CATEGORIES } from '../../../../src/core/utils';
 
 export const graph: LegacyPluginInitializer = kibana => {
   return new kibana.Plugin({
     id: 'graph',
     configPrefix: 'xpack.graph',
-    publicDir: resolve(__dirname, 'public'),
     require: ['kibana', 'elasticsearch', 'xpack_main'],
     uiExports: {
-      app: {
-        title: 'Graph',
-        order: 9000,
-        icon: 'plugins/graph/icon.png',
-        euiIconType: 'graphApp',
-        main: 'plugins/graph/index',
-        category: DEFAULT_APP_CATEGORIES.analyze,
-      },
-      styleSheetPaths: resolve(__dirname, 'public/index.scss'),
       mappings,
       migrations,
     },

x-pack/legacy/plugins/graph/README.md → x-pack/plugins/graph/README.md

@@ -8,7 +8,7 @@ Graph shows only up in the side bar if your server is running on a platinum or t
 
 * Run tests `node x-pack/scripts/jest.js --watch plugins/graph`
 * Run type check `node scripts/type_check.js --project=x-pack/tsconfig.json`
-* Run linter `node scripts/eslint.js x-pack/legacy/plugins/graph`
+* Run linter `node scripts/eslint.js x-pack/plugins/graph`
 * Run functional tests (make sure to stop dev server)
   * Server `cd x-pack && node ./scripts/functional_tests_server.js`
   * Tests `cd x-pack && node ../scripts/functional_test_runner.js --config ./test/functional/config.js --grep=graph`
@@ -21,7 +21,6 @@ Currently most of the state handling is done by a central angular controller. Th
 
 * `angular/` contains all code using javascript and angular. Rewriting this code in typescript and react is currently ongoing. When the migration is finished, this folder will go away
 * `components/` contains react components for various parts of the interface. Components can hold local UI state (e.g. current form data), everything else should be passed in from the caller. Styles should reside in a component-specific stylesheet
-* `hacks/` contains files that need to run before the actual app is started. When moving to the new platform, this folder will go away.
 * `services/` contains functions that encapsule other parts of Kibana. Stateful dependencies are passed in from the outside. Components should not rely on services directly but have callbacks passed in. Once the migration to redux/saga is complete, only sagas will use services.
 * `helpers/` contains side effect free helper functions that can be imported and used from components and services
 * `state_management/` contains reducers, action creators, selectors and sagas. It also exports the central store creator

x-pack/plugins/graph/kibana.json

@@ -4,7 +4,7 @@
   "kibanaVersion": "kibana",
   "server": true,
   "ui": true,
-  "requiredPlugins": ["licensing"],
+  "requiredPlugins": ["licensing", "data", "navigation"],
   "optionalPlugins": ["home"],
   "configPath": ["xpack", "graph"]
 }