* [babel] create babel-preset and babel-register modules
* [babel-preset] add comments to babel-preset-env.target choices
* [babel-preset] use more normal BUILT_WITH_BABEL signal
* [babel-register] extended comment about filtering ./src in dist
* [babel-preset] stage of class properties has changed, sorta
* adding tabify response handler
* tabify should be the default response handler
* asAggResultConfig should be configurable for BWC
* update table to work with new tabify response handler
* region map needs to define responseHandler: none
* fixing tests
* markdown should set responseHandler to none
* Remove unused doc source code
Ever since the saved object api was introduced, we’ve been using that,
or querying es directly, for mget data.
* Remove commented out code
* Stop using onError because there is a memory leak there
* Restart segmented fetch errors.
* Get rid of all onError calls
* Remove unused functions
* Continue searching when a doc_table error is encountered
Otherwise a single saved search failure won’t try again when it’s on a
dashboard. The previous implementation handled this via the
request.retry in the default errorHandler.
* Fix lint error
* don't pass resolve and reject into inner function
Prior to 5.6, we would push mappings once the object type was used. Since we are now ensuring all mappings are set, there is a situation where a field with type string exists but we are pushing text.
You can not have a field with the same name, but different data type, in two different document types.
To resolve this, we are setting update_all_types when updating mappings.
Backport of #13991
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
After some trial and error trying to build a generic API that could control both kuery and legacy filters I decided it wasn't going to work well. So instead I'm taking a different approach. I'm making kuery available to visualizations alongside the existing queryFilter. Visualizations can choose to support one or both. Eventually we can just deprecate and remove queryFilter from the vis API. The standard filter_bar_click_handler still supports both, so basic visualizations that rely on that behavior will just work.
The vis API has two new members:
queryManager - contains two simple methods, one for getting and the other for setting the current app level query.
kuery - all of the functions exported by the kuery module, made available so visualization plugins don't have to import them directly from kibana
The addition of these two members should provide visualizations with everything they need to read, modify, and update kuery queries.
When functional testing UIs that contain this component for pagination, we need a way to get a handle on the "previous page" and "next page" buttons. So we add test subject attributes to these buttons' elements.
index.mapper.dynamic should not be used for 6.0+ indices, so this commit
removes it from the esArchiver mappings.json for kibana
Related elastic/elasticsearch#25734
* Remove field selection restriction for cardinality
* fixing a bug with filter ratio where not selecting a metric.field throws a fatal
* Adding tests; fixing bug
Since the title of the missing pattern is unknown (because it's missing) we can't display it, but we can improve the error slightly by including the name of the pattern that is being loaded instead. I've added that, in addition to the ID so there's no confusion if the titles are the same.
We already have "BSD-3-Clause" as a valid license, but there's a variant
with a space instead of a '-' being used by js-base64 that we need to
accomodate for.
* Move htmlIdGenerator to ui_framework
* Use jest expect instead of chai
* Add htmlIdGenerator to accessibility styleguide
* Improve the writing of the accessibility styleguide
