-
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
Migrate reporting top nav to sharing context menu #22596
Conversation
💔 Build Failed |
💔 Build Failed |
@elastic/kibana-design Where should the feedback go when the user clicks the generate button? Right now a toast notification is displayed. @cjcenizal suggested disabling the button and displaying the message in the context menu. I like that idea since it puts the feedback closer to where the action takes place. What do you think? |
I just thought of one problem with my idea of disabling the button... if the user has auto-refresh enabled and wants to create a series of PDFs as the data changes, then disabling it on click will be frustrating. |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
💔 Build Failed |
bootstrap error
|
jenkins, test this |
💔 Build Failed |
jenkins, test this |
💔 Build Failed |
💔 Build Failed |
jenkins, test this |
💔 Build Failed |
💔 Build Failed |
flaky x-pack security test
jenkins, test this |
💚 Build Succeeded |
💔 Build Failed |
Same xpack rbac test failure. @elastic/kibana-security Is this a known flaky test?
jenkins, test this |
@Rasroh is this the flaky test you wanted to debug with me? |
💚 Build Succeeded |
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.
Couple minor things but otherwise, LGTM. Did not pull down and test latest code.
src/ui/public/share/share_action.ts
Outdated
readonly id: string; | ||
|
||
getShareActions: ( | ||
{ objectType, objectId, getUnhashableStates, sharingData, isDirty, onClose }: ShareActionProps |
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.
Interesting way to do this. Since it's just defining the interface and ShareAction, I think you could get away with:
getShareActions: (config: ShareActionProps) => ShareAction[]
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.
not sure if you are looking at an old commits, but the destructuring was removed in this commit
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.
Sorry, that was an old unpublished comment that got published by accident with the latest :)
const query = { | ||
jobParams: rison.encode(jobParams), | ||
}; | ||
return kfetch({ method: 'POST', pathname: `${API_BASE_URL}/${exportType}`, query }).then( |
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.
I think if you make this an async function and use await the returned promise is implicit. Should still work with the catch. E.g.
const response = await kfetch({ method: 'POST', pathname: `${API_BASE_URL}/${exportType}`, query });
jobCompletionNotifications.add(response.job.id);
I don't think you need to return the response, just the promise.
* you may not use this file except in compliance with the Elastic License. | ||
*/ | ||
|
||
// TODO: Remove once typescript definitions are in EUI |
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.
I think you can remove this comment, there is no declaration here, so I think these defintions are typed in eui
💚 Build Succeeded |
cc @w33ble Not sure how this is going to impact canvas/reports. |
💔 Build Failed |
@@ -85,6 +85,7 @@ | |||
"@kbn/ui-framework": "link:../packages/kbn-ui-framework", | |||
"@samverschueren/stream-to-observable": "^0.3.0", | |||
"@slack/client": "^4.2.2", | |||
"@types/moment-timezone": "^0.5.8", |
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.
@nreese Do you mind if I move this to devDependencies?
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.
Not at all. Thanks @sqren. Putting it in dependencies
was a mistake
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.
No worries. I just noticed as I was adding some types.
Dev Docs
exportTypesRegistry
removedRemoved
exportTypesRegistry
from the client-side.exportTypesRegistry
had been used for registering Reporting export types for the UI.exportTypesRegistry
still exists for registering export types with the server.