Data views - saved object client use resolve instead of get#108637
Data views - saved object client use resolve instead of get#108637mattkime merged 18 commits intoelastic:masterfrom
resolve instead of get#108637Conversation
resolve instead of get
|
@elasticmachine merge upstream |
|
waiting for #111201 to be resolved first |
|
@elasticmachine merge upstream |
resolve instead of getresolve instead of get
|
Pinging @elastic/kibana-app-services (Team:AppServices) |
ppisljar
left a comment
There was a problem hiding this comment.
can you please add a test for this, apart from that LGTM
note: can you please also open an issue to deduplicate this whole file into common folder ?
I'm not sure what you mean. The error class is in common but both implementations are server and client specific. There could be a little more code reuse but I think the number of lines of code would be the same in the end. |
|
saved_objects_client_wrapper.ts in server and public look pretty much the same ? |
The differences are important. I'm open to specific suggestions. |
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Page load bundle
Unknown metric groupsAPI count
References to deprecated APIs
History
To update your PR or re-run it, just comment with: |
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
…tic#108637) * so client - use resolve instead of get Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Summary
Closes #108335
Data views service should use
resolveinstead ofgetendpoint and pass on correct error if there's a conflict.