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
Fix removing a single field formatter #141078
Conversation
Pinging @elastic/kibana-app-services (Team:AppServicesUx) |
💚 Build Succeeded
Metrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
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.
Nice, I like this effort compared to mine as its much simpler. code changes look good!
Worth backporting to 8.4 |
(cherry picked from commit f44f1d1)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
* main: [SearchBar] Allow show refresh button as an icon (elastic#141088) [Files] Added usage counters for delete, unshare and download (elastic#140091) Fix removing a single field formatter (elastic#141078) [APM] Move service metric config to kibana advanced settings (elastic#141147) Synthetics project update improvements (elastic#140990)
Summary
fix #134873
When updating a data view saved object, make sure we send an empty field format object instead of an undefined one when there are no field formats.
I think the fix makes sense, especially considering that this is how we treat
sourceFilters
andruntimeFieldMap
I saw this attempt to fix it #134874, but it looks like it is a more risky change