-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate legacy vars when rendering all applications #54768
Conversation
Pinging @elastic/kibana-platform (Team:Platform) |
Can we add a better e2e test that covers this case? Should validate that the custom bundle rendering endpoint not only returns a 200, but successfully loads the client-side application. |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
ACK: testing my use case with this PR... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue reported in #54470 seems to be fixed for me now, thanks!
@eliperelman @pgayvallet but when I render chromeless app in non-auth context something sends request to api/core/capabilities
that leads to a fatal error as well (request fails with 401
). Even if I use includeUserSettings: false
. Is it related to this PR or it will be handled separately?
@azasypkin related to the second point of #51956. See also #51438 (comment) If your route is anonymous, you are supposed to register it using Exemple in |
Ah, right, completely forgot, thanks! |
* Generate legacy vars when rendering all applications * Move rendering functional tests and add user settings tests * Make rendering integration tests more robust, get data from page * Address review nits, fix CI failures * Remove extraneous file * Fix type error
* Generate legacy vars when rendering all applications * Move rendering functional tests and add user settings tests * Make rendering integration tests more robust, get data from page * Address review nits, fix CI failures * Remove extraneous file * Fix type error
* Generate legacy vars when rendering all applications * Move rendering functional tests and add user settings tests * Make rendering integration tests more robust, get data from page * Address review nits, fix CI failures * Remove extraneous file * Fix type error
* Generate legacy vars when rendering all applications * Move rendering functional tests and add user settings tests * Make rendering integration tests more robust, get data from page * Address review nits, fix CI failures * Remove extraneous file * Fix type error
…t-of-legacy * 'master' of github.com:elastic/kibana: (142 commits) [Vis] Move Timelion Vis to vis_type_timelion (elastic#52069) Deprecate `chrome.navlinks.update` and add documentation (elastic#54893) [ML] Single Metric Viewer: Fix time bounds with custom strings. (elastic#55045) [Vis: Default editor] EUIficate and Reactify the sidebar (elastic#49864) [Mappings editor] Fix cannot set boolean value for "null_value" param (elastic#55015) [SIEM] Adds support for apm-* to the network map (elastic#54876) [Reporting] Define shims of legacy dependencies (elastic#54082) Resolver is overflow: hidden to prevent obscured elements from showing up (elastic#55076) Upgraded EUI to 18.2.1 (elastic#55090) [Maps] Support styles on agg fields with _of_ in name (elastic#54965) Remove xpack_main requirement, it's no longer in use (elastic#55060) Fix Snapshots Policies Alignment Issue in IE11 (elastic#54866) first rule cuts (elastic#54990) [DOCS] Adds geocentroid note to coordinate map (elastic#54389) [Canvas] Fixes the Copy Post Url link (elastic#54831) Fixes bugs with full screen filters (elastic#54792) [ML] Fix decoding in the URL state (elastic#54915) Remove redundant `x-pack/typings`. (elastic#55042) [SIEM][Detection Engine] Adds critical missing status route to prepackaged rules Generate legacy vars when rendering all applications (elastic#54768) ... # Conflicts: # x-pack/plugins/translations/translations/ja-JP.json # x-pack/plugins/translations/translations/zh-CN.json
* Generate legacy vars when rendering all applications * Move rendering functional tests and add user settings tests * Make rendering integration tests more robust, get data from page * Address review nits, fix CI failures * Remove extraneous file * Fix type error
Summary
Fixes #54470.
Dev Docs
Rendering any type of application, even ones for the new platform, should still generate legacy vars injected into the page metadata, and this ensures these vars are injected for HTTP route rendering as well.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.This was checked for cross-browser compatibility, including a check against IE11Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n supportThis was checked for keyboard-only and screenreader accessibilityFor maintainers