-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Graph] Deangularize saved object handling (workspace) #52529
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
[Graph] Deangularize saved object handling (workspace) #52529
Conversation
…-22-np-saved-object
…-22-np-saved-object
|
jenkins, test this |
|
@elasticmachine merge upstream |
flash1293
left a comment
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 still works fine - LGTM besides one small nit
| */ | ||
|
|
||
| export function extractReferences({ attributes, references = [] }) { | ||
| import { SavedObjectAttributes, SavedObjectReference } from 'kibana/server'; |
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 should not be imported from the server as this is client side code: import { SavedObjectAttributes, SavedObjectReference } from 'kibana/public'; - this will soon trigger a linting error
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.
Thanks! 👍 I've changed that
…om:kertal/kibana into kertal-pr-2019-12-09-np-saved-object-graph
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
Summary
Follow up of #51562, deangularization and typescriptification of the
saved_objectusage ingraphChecklist
Use
strikethroughsto remove checklist items you don't feel are 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 accessibilityFor maintainers
- [ ] This was checked for breaking API changes and was labeled appropriately