* Only throw the error about building the DLL if we're not running in Jest
* Update existing storyshots
* Add Jest mock for Datasource story
All tests look to be passing and `yarn storybook canvas` works. I clicked through all the stories and it doesn't look like anything is broken.
* Reused the naming scheme for field column in conditions table.
* Updated snapshot.
* update Operator value to show as `is`
* Update Jest snapshot
Co-authored-by: Paul Tavares <paul.tavares@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Removed skip on alerting e2e tests
* Reduced alerting tests execution time by removing page reload for each test. Added server side cleanup fo each test with createAlert. Removed long waiting toast method for reduce flakiness.
* Added additional cleanup and retry method for delete single alert
* Prevent react warnings for unknown `isVisible` prop
Unknown config options ultimately become attributes on an anchor/button
element, so we need to not overload these config objects.
* Fix react warning about unknown `isDisabled` prop
There is no `isDisabled` prop on the underlying `EuiFieldText`
component, so we should use the native `disabled` attribute instead.
* Fix warning about switching between un-/controlled componenents
On the first few renders, our input refs have not been set while a
default value has, so the length of our values is 1 while our refs is 0.
This causes us to hit the 'else' condition of our ternary, leading to an
input with no value. When the ref is then populated, a value is
generated and so is the error.
The previous logic here was always evaluating to `value: item` and so was
simplified.
* Fix jest warning on unexpected state update
* removes unnecessary use of act()
* renders our component within the test
* This allows our test to synchronize with react and prevents the
warning; I suspect it has something to do with the scoping of
`wrapper` or the `beforeEach` not being async, but I haven't had
time to investigate.
* Remove unnecessary test guards
These tets no longer throw warnings.
* add functional test for searchBar filters. remove boolean schema from datagrid
* always use string version of key for charts
* add schema back in for histogram label
* use ?? instead of || for undefined check
* Add cancel button in the visualize editor
* Fixing i18n namespace
* Always show cancel button
* Always show cancel button
* Adding a fucntional test
* Show confirm dialog only if there are unsaved changes
* Show confirm modal only if there are changes
* Add onAppLeave handler and ditch confirmModal
* Fix functional test
* Only use onAppLeave if coming from dashboard/canvas
* Add actions.default to onSave and onSaveAndReturn
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* show error when clone fails due to no index pattern
* default results_field unless specified
* results field switch set to on if resultsField for cloned job is default
* ensure cloned job config not overwritten in advanced editor
* show errorToast if unable to clone anomalyDetection job due to no indexPattern
* ensure jobConfig query getting saved in form state
* ensure index patterns with commas handled correctly
* clone should accept comma separated index patterns
* use nullish coalescing operator when checking for undefined analysisFields
Renames "Built-In Alerts" feature to "Stack Alerts" and "Actions" feature to "Actions and Connectors" as we've decided these names make more appropriate and better communicate what these features are.
resolves https://github.com/elastic/kibana/issues/72058
Finally, we're logging the action executor error responses to the Kibana log.
We have not been doing this previously, out of an abundance of caution. The
message written may contain data returned from a 3rd party service call, and
we weren't sure this would be "safe" to log, in a PII sense.
After several minor releases, and seeing these service messages in the event
log for almost all the built-in action types, we've decided they are "safe" and
it's time to add them, as they provide some **very** helpful diagnostic
feedback to customers.
* Remove APM stacktrace snapshots
These are not necessary and have caused problems for other contributors. Replace the snapshots with tests that check for errors or the structure of the results.
Move the test files out of the __test__ directory and rename the directory to __fixtures__.
* Refactored store code to group properties related to location so that would be easy to introduce a new view type parameter.
* Added view type to the location and routing.
* Added a simple hook to make navigation easier.
* Improved the navigation hook to get params.
* Some fix for double notification after creating trusted app.
* Added a hook to perform trusted app store actions.
* Fixed trusted app card delete callback.
* Added grid view.
* Fixed the stories structuring.
* Shared more logic between grid and list.
* Finalized the grid view.
* Flattened the props.
* Improved memoization.
* Moved the flex item elements inside conditions.
* Fixed broken stories.
* Updated the snapshot.
* Updated the snapshot.
