While in production, we use the `no-warnings` flag to prevent warnings from going to STDERR, and instead capture the warning events using our logger. Some warnings are helpful in debugging and/or identifying problems in production, like UnhandledPromiseRejection. Deprecation warnings are not an immediate problem, but an issue with upgrading to the next version of Node. These warnings will continue to be presented to developers, just not for production users.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* add more output
This will let us know if the filter is failing to be added on the
visualization before being saved.
* run 20x
* go back to single run
The addition of the optional flag to disable leading wildcards inadvertently broke exists queries, which are accomplished in kuery with the fieldName:* syntax.
Lukas and I chatted over Slack and we both agreed it didn't really make sense to apply query:queryString:options to query_string filters. If someone is using the advanced query DSL editor to create a query_string filter they probably want full control over it.
This is a breaking change so it will only go in 7.0. In 6.x users should use one of the workarounds.
* advanced setting to control search request preference
* add header tests
* add sentince about caching to description
* change courier:setRequestPreference to list and add courier:customRequestPreference
* update setting text
* [kbn-dev-utils/procRunner] try using execa to avoid never-exitting procs
* [kbn-dev-utils/procRunner] don't listen for close event, rely on stdio streams ending
* separate implicit connection between app state panels and redux tree panels.
They are now two different objects. This will help pave the way to
removing so much apostate in view mode where it isn’t necessary
* remove console output
* fix tests and propagate dashboard title & description
* Clean up with review comments
* use reduce instead of map so the array becomes an object
* Remove child/parent state concept in persistedStateProvider
Looks like the only time it was used was when dashboard created child
ui states for visualize and saved searches. We’re now all handling
this state passing via the embeddable layer.
* Remove more parent/child tests
* Remove extra spot that referenced the two removed parameters
* adding large_string_test
* removed a failing test, modified the existing one
* new line at the end of mappings.json
* removed the data.json file and also removed the navigateTo() and clickKibanaIndices() as createIndexPattern() takes care of it
* more modifications
* Clone the moment object before using it to generate reporting data
so that calling .utc() doesn't mutate global state.
* fix tests
* do less work on each digest cycle
