* 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.
In order for the runbld project we use in CI to auto-discover the junit reports we generate they need to match `TEST-*.xml`, which will allow us to include more details in the failure emails, and push failure info to the build-stats cluster.
* Support legacy use cases for passthrough
* Support generic case too
* Add legacy flag
* Do not format api field names in legacy mode
* Add basic test for legacy parameter
* Add more tests
* Ensure we pass down the expiry_date for the license
* Update tests
* Update fixtues
* Update fixture
* Revert "Update fixture"
This reverts commit 0a1e7a5b29.
* Revert "Update fixtues"
This reverts commit b0c0e70200.
* Revert "Update tests"
This reverts commit 6a4421bb4e.
* Revert "Ensure we pass down the expiry_date for the license"
This reverts commit 2562395a78.
* Use expiry_date_in_millis value instead of expiry_date
This upgrades prettier to version 1.14.0. The main motivation is to gain support for the new TypeScript language features introduced in 2.9 and 3.0.
Prettier versions 1.13 and 1.14 also introduced some other JavaScript and TypeScript style improvements resulting in a few small line break and parenthesis changes.
The relevant release notes are:
* [Prettier 1.13.0 Release Notes](https://prettier.io/blog/2018/05/27/1.13.0.html)
* [Prettier 1.40.0 Release Notes](https://prettier.io/blog/2018/07/29/1.14.0.html)
Fixes#21416 - this is identical to https://github.com/elastic/kibana/pull/21402, but adds testing to prevent a regression.
@chrisronline in the interest of speed, time, and stability for 6.4, I opted not to do a full functional test, but rather an API test to ensure that the API endpoint was interacting with the Saved Objects Client as expected.
* Move EuiComboBox utility functions into its own service
* remove old functions from visualize page object
* use waitForDeletedByClassName instead of retry and exists to ensure no longer loading
* wait for options loading when getting options list
* Integrate i18n-engine into "Index Patterns" tab
* Adjusted unit tests for "Index Patterns" tab
* Localization of "Index patterns" section name
* Rename the function shallowIntl to shallowWithIntl, remove needless check for translation type id
* Refactoring of default message
* Localization for FieldEditor component
* Adjust unit tests for FieldEditor component
* Integrate i18n-engine into "Index Patterns" tab
* Adjusted unit tests for "Index Patterns" tab
* Localization of "Index patterns" section name
* Rename the function shallowIntl to shallowWithIntl, remove needless check for translation type id
* Refactoring of default message
* Localization for FieldEditor component
* Adjust unit tests for FieldEditor component
* Replace I18nContext to injectI18n according to changes in @kbn/i18n
* Fix broken saving form
* Adjust components importing according to changes in @kbn/i18n
* Formatting and refactoring
* Update ids
* Fix invalid HTML and refactoring
* Use i18n module instead of AngularJS service
* Localize scripting_syntax.js, refactoring
* Update message ids.
* fix plural form in status messages
* fix messages in status message, _field component
* move back span in time_field
* refactor enzyme helper for providing intl into context
* do not translate Painless
* test call params in formatMessage
* clear formatMessage mock after each test
Co-authored-by: maryia-lapata <mary.lopato@gmail.com>
This fixes the "Export Everything" button on the Saved Objects Management screen so that the export properly constrains the saved object types returned.
Previously, this endpoint was incorrectly returning objects that were not requested (such as the `config` object). This behavior is exacerbated with [Spaces](https://github.com/elastic/kibana/issues/18948) because the export button would incorrectly export the Space objects, which in turn do not make sense to import.
