-
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
Move Lens saved object setup to Kibana platform #61157
Conversation
getTitle: (obj: { attributes: { title: string } }) => obj.attributes.title, | ||
getInAppUrl: (obj: { id: string }) => ({ | ||
path: getEditPath(obj.id), | ||
uiCapabilitiesPath: 'visualize.show', |
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.
ℹ️ We used before this move lens.show
here, which was wrong, since there is no lens.show
uiCapabilities. We decided that time to use the visualize uiCapability for Lens, it seemed just this place always returned the wrong capability.
💚 Build SucceededTo update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-app (Team:KibanaApp) |
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.
Tested and works, LGTM
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.
Haven't tested, but this LGTM
Summary
Move the Lens saved object registration from the legacy world to Kibana platform.
For QA: The only functional change this introduces is that Lens Saved Objects (in Management > Saved Objects) will now have an icon and can be clicked to view them in Lens.
Checklist
Delete any items that are not applicable to this PR.
[ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support[ ] Documentation was added for features that require explanation or tutorials[ ] Unit or functional tests were updated or added to match the most common scenarios[ ] This was checked for keyboard-only and screenreader accessibility[ ] This renders correctly on smaller devices using a responsive layout. (You can test this in your browser[ ] This was checked for cross-browser compatibility, including a check against IE11For maintainers
[ ] This was checked for breaking API changes and was labeled appropriately