* break dependency on data plugin TS code
* move global typings to @kbn/utility-types
* import types from @kbn/utility-types
* remove type dependency on plugins
* add intermediate js files to break dependency on outter TS code
* temp type declaration for query-string
* declare src/core project
* export types to reference in the built d.ts files
* reference core project
* move jest types out of kbn/utility-types due to a clash with mocha types
* fix wrong es_kuery path and ts project paths
* reference core from packages consuming it
* x-pack & oss should use the same lodash version
* Revert "x-pack & oss should use the same lodash version"
This reverts commit 79cec5781e.
* use the same lodash version
* fix @types/lodash TS2300: Duplicate identifier error
* fix wrong imports
* update docs
* update docs
* add a comment why file is needed
* Adding dashboard as dependency to visualize
* Making visualize embeddable as ReferenceOrValueEmbeddable
* Adding attribute service to visualize embeddable
* Binding createFromSavedObject method
* Add/remove visualize embeddable from library
* Removing debugger statement
* Using custom save method on attribute service
* Reverting to not using attribute service
* Resetting flag value
* Fix i18n title and update title
* Using custom save method on attribute service
* Fixing eslint
* Using custom save method in visualize embeddable factory
* Making getInputAsValueType return Promise as it should
* Better error handling when saving a visualization fails
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
The Alerts Authorisation now manually builds the authorization filter instead of parsing a KQL string in order to get around the performance issue we recently identified in KQL.
* Add route to accept a direct package upload.
* Only accept application/zip or application/gzip
* Use better name for response containing only a message.
* Add integration test for direct package upload.
* [APM] Remove useLocation and some minor route improvements
* Replace `useLocation` and our `LocationContext` with `useLocation` from React Router. We can do this since we're now using the platform history, added in #76287.
* Pass in `RouteComponentProps` where appropriate to routes to use `history` and `location`.
This is in the service of #51963, but doesn't do anything with `useUrlParams` or any of the other changes specified in that issue.
* Update/refactor EnterpriseSearchRequestHandler to manage internal endpoint error behavior
+ pull out / refactor all errors into their own methods instead of relying on a single 'error connecting' message
* Fix http interceptor bug preventing 4xx/5xx responses from being caught
* Add handleAPIError helper
- New and improved from ent-search - this one automatically sets flash messages for you so you don't have to pass in a callback!
* Fix type check
* [Feedback] Add option to queue flash messages to handleAPIError
- Should be hopefully useful for calls that need to queue an error and then redirect to another page
* PR feedback: Add test case for bodies flagged as JSON which are not
* Rename handleAPIError to flashAPIErrors
* Move remaining uses of serviceName away from urlParams
There were a few of these that were either missed or lost in merge conflict resolution.
I went through everything that's used as a path parameter and made sure it wasn't being used anywhere with `urlParams`.
Previously none of the charts were working, now they all are.
Looks like #67791 introduced a find/replace change that broke APM's e2e tests. This reverts that change.
* Handle no mappings found for sort and collapse fields
* Add comment
* Fix sort usage
* Ensure we query off MB for new api calls as well
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* [ML] fix custom urls processing for security app
* [ML] improve query string parsing
* [ML] remove escaping with !, adjust a unit test for security app
* [ML] unit test
* [ML] unit test
- Adds schema definitions to transform API endpoints and adds API integration tests.
- The type definitions based on the schema definitions can be used on the client side too.
- Adds apidoc documentation.
