-
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
Remove kibana yml settings workaround in input control vis #67464
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
This might not be the right approach after all - soon there will be a specific API to fetch auto complete values, so we can just use that instead of using the search service in a hacky way. |
The API |
I think it's fair to close this issue - we don't plan on changing anything on the legacy input controls, and all hacky code will get completely removed once we can finally remove them for good 👍 |
In #63443 it was necessary to implement a workaround for passing some kibana.yml settings to the client using a new API route. This should be removed and replaced by the core
exposeToBrowser
functionality. This depends on #66085Locations in code:
The text was updated successfully, but these errors were encountered: