* EnterpriseSearchRequestHandler: Create new hasJsonResponse param - in place of try/catch previously added for an empty response - we should instead attempt to handle all non-JSON responses manually, as they're (currently) the outlier * Update AS sample engine/onboarding route with hasJsonResponse: false - as this was the original route that added the try/catch - should still work without it now * Update WS source download diagnostic route with hasJsonResponse: false - this was the original impetus for the non-JSON feature request - WS needs the ability to download JSON files directly * Update Download Diagnostics filename to match standalone UI * Fix misc routing issues in Source Settings - `/api` route is missing Kibana basepaths (affects both dev modes and users who have Kibana canonically set to a non-root URL) - We shouldn't be using RR's native <Link>, but instead our RR helpers which use Kibana's instance of RR history |
||
---|---|---|
.. | ||
applications | ||
index.ts | ||
plugin.ts |