src/platform/plugins/shared/home/README.md
Moves the legacy ui/registry/feature_catalogue module for registering "features" that should be shown in the home page's feature catalogue to a service within a "home" plugin. The feature catalogue refered to here should not be confused with the "feature" plugin for registering features used to derive UI capabilities for feature controls.
Replaces the legacy ui/registry/feature_catalogue module for registering "features" that should be showed in the home
page's feature catalogue. This should not be confused with the "feature" plugin for registering features used to derive
UI capabilities for feature controls.
// For legacy plugins
import { npSetup } from 'ui/new_platform';
npSetup.plugins.home.featureCatalogue.register(/* same details here */);
// For new plugins: first add 'home` to the list of `optionalPlugins`
// in your kibana.json file. Then access the plugin directly in `setup`:
class MyPlugin {
setup(core, plugins) {
if (plugins.home) {
plugins.home.featureCatalgoue.register(/* same details here. */);
}
}
}
Note that the old module supported providing a Angular DI function to receive Angular dependencies. This is no longer supported as we migrate away from Angular and will be removed in 8.0.
Replaces the sample data mixin putting functions on the global server object.
timeFieldsElasticsearch index names are prefixed with kibana_sample_data_. For more details see createIndexName
Sample data sets typically provide data that spans 5 weeks from the past and 5 weeks into the future so users see data relative to now for a few weeks after installing sample data sets.
Use existing sample data sets as examples. To avoid bloating the Kibana distribution, keep data set size to a minimum.
Follow the steps below to add new Sample data sets to Kibana.
plguins.home.sampleData.registerSampleDataset(yourSpecProvider) in your setup method where yourSpecProvider is a function that returns an object containing your sample data spec from step 4.