-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Expose serverBasePath
on client-side
#57583
Comments
Pinging @elastic/kibana-platform (Team:Platform) |
What is the difference with |
As far as I can tell, I imagine we'll want to expose a dedicated Having access to |
You are right. Adding that to the injected metadata should be trivial. (notes for later:) Server
kibana/src/core/server/http/base_path_service.ts Lines 46 to 49 in 01ac90f
Client kibana/src/core/public/injected_metadata/injected_metadata_service.ts Lines 112 to 116 in 071db79
kibana/src/core/public/http/base_path.ts Lines 40 to 45 in 4980387
|
Similar to #45991, Spaces needs access to the serverBasePath on the client-side. We should add this to the
core.http.basePath
interface in the browser.The text was updated successfully, but these errors were encountered: