-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Get rid of saved object loader #112635
Get rid of saved object loader #112635
Conversation
savedObject.searchSourceFields = searchSourceValues; | ||
} | ||
} catch (error: any) { | ||
if ( |
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.
@VladLasitsa this stuff is only necessary for the legacy import - we need to create a valid saved vis instance which captures the error state. As this won't be used for legacy import, we can just bubble up the error.
const savedObject = { | ||
id, | ||
displayName: SAVED_VIS_TYPE, | ||
getEsType: () => SAVED_VIS_TYPE, |
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.
This is probably true for a bunch more places, but I think some of that cruft is not necessary anymore.
@elasticmachine merge upstream |
user doesn't have permission to update head repository |
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Any counts in public APIs
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
References to deprecated APIs
History
To update your PR or re-run it, just comment with: |
Closed because will opene new PR myself: #113121 |
tbd