* Convert xpack license check to use banners service.
* Remove notifier directive method.
* Remove notifier banner directive.
* Simplify pullMessageFromUrl and move it into its own appRedirect module.
* [core/public/legacyPlatform] render into a child of the rootDomElement
* [kbn-chrome] use #kibana-body selector for ensuring root height
* after feedback in #20752, clear elements by setting textContent
* [browserTests] mount CoreSystem in a child, we require stuff in <body>
* [core/public] ensure the rootDomElement is full-screen
* add some comments tieing together root style rules
* use `readonly` for unchanged properties
* avoid unnecessary recreation of default param
* comment about why coreSystem is not rendered into body in the tests
* use more destructuring
* rename argument in callback type signature
* fix typo
* [core/public/styles] switch from less to css
a36b87a#diff-aff92ff718af4b68d02f030d8a438754 added an ng-if around the available fields button element. ng-if creates a child scope. The ng-click on the button directly modifies scope state. As a result, when the ng-if was added, that ng-click began modifying the ng-if's child scope instead of the parent scope.
The best solution would be to update the discFieldChooser directive to use the controllerAs property so its scope variables are namespaced. However, this is a bit risky because I'd need to make sure to update every single scope variable reference in the template, and it's a relatively large template. Since we'd like to backport this to 6.4 I've taken the less risky route of adding $parent to the scope reference inside the ng-if block.
* trying new EuiWrappingPopover
* allow button press to close popover
* fix button styling
* start options panel with darkTheme option
* add other options
* remove old options html
* get dashboar state functional test working
* Convert info button and the rest of the page to EUI
* Update other overview pages
* Use Page directive
* Give the tooltip some more space
* Add page body to a couple places
* PR feedback
* Convert beats overview page to use EUI components
* More UI components for beats overview
* Set background color to white
* Update snapshots
* Add PageBody wrapper
* Update snapshots
* Use panels
* PR feedback
* Update snapshots
* Turn reporting snapshot tests back on with new baselines
* Use snapshots generated from chromium. Bump the threshold so phantom comparisons pass
* Increase timeouts because of chromium functional tests.
* remove accidentally checked in session snapshots
* add a better vis baseline, run once through at 0 to check expected threshold
* turn on verbose logs
* Use threshold, turn debug mode on in jenkins
* Wrap both convert pages in the retry
* Update baselines
Preserve layout one got messed up - it was actually a print layout.
* bump threshold even more
* use SavedObjectsClientProvider to provide SavedObjectLoader with an angular wrapped saved object client
* Improve filterBar.addFilter performance
* Add better documentation
* Ease logic of addFilter and add better docs
* Fix old addFilter calls
* [kbn-test] convert kibana-install-dir flag to installDir option
* [kbn-test] replicate kibana-install-dir handling to startServers
* [ftr] try running functional tests in production in CI
* Revert "[ftr] try running functional tests in production in CI"
This reverts commit e5b94aa024.
* [core/public/legacyPlatform] exclude ui/test_harness from the distributable
* [optimizer] fix `process.env.IS_KIBANA_DISTRIBUTABLE` definition
* [optimizer] only define `process.env.IS_KIBANA_DISTRIBUTABLE` when needed
Adding a `webpack.DefinePlugin` slows down the optimizer a small amount,
so only apply it when it is necessary, and skip it if it is going to
be defined as "false".
* [kbn-test/startServer] don't run in --dev mode if running from dist
* [ftr/kibanaServer/version] attach `-SNAPSHOT` suffix to version if running build_snapshot
* Remove implementation detail assertion from objects table test.
* Reset selection state when table state or query state changes.
* Remove total count from title.
* Add support for vertical axis
The vertical axis scale has an inverted range (max, min) and we need to compute the absolute scale width instead.
* Add functional test for Y axis scale type switching
* Remove unnecessary waitUntilLoadingHasFinished
* set kibana locale in kibana.yml config
* remove accept-language-parser
* remove unnecessary tests
* fix readme description, fix description for locale in kibana.yml
* add point, that i18n.locale option should have exact match
* update kbn/i18n README
* Update README.md
* use getUiTranslations in render_mixin, remove i18n_mixin
* move registering translation files to mixin function
* set pause to 'true' when refresh interval is zero
* keep original assertion
* fix expect message in functional tests now that pause is set to true
* fix executorProvider mocha test
* add if check around using async loaded object in VisEditorVisualization
* immediatly call _handler.update when handler is loaded and update has occured
* add jest test
* lint fixes
* remove sinon
* move global state update from kbn_global_timepicker to timefilter
* add functional test
* update time and refreshInterval when either update
* use same function name from kbn_global_timepicker
* call globalState.save in context of a digest cycle
* ensure callers of registerTimefilterWithGlobalState pass in
- Enables support for the rare detector for the charts in Anomaly Explorer and Single Metric Viewer.
- The charts use a count aggregation. The anomaly records for rare detectors include actual/typical values, but they don't refer to values we have for other detectors. actual is always 1 and doesn't refer to the actual count. typical has the probability as its value. To avoid confusing users by displaying these values as actual/typical in the tooltip, just the value of count of the aggregation will be shown.
- This enables the existing charts to be able to visualize rare detectors. A follow-up to this PR will introduce a specific chart for rare detectors.
