remove legacy uiSettings mixin #76255
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pgayvallet
added
Feature:Legacy Removal
Contributor
Contributor
|
Pinging @elastic/kibana-platform (Team:Platform) |
mshustov
approved these changes
Aug 31, 2020
pgayvallet
added a commit
to pgayvallet/kibana
that referenced
this pull request
Aug 31, 2020
* remove legacy uiSettings mixin * adapt ui_render mixin to use core APIs
pgayvallet
added a commit
that referenced
this pull request
Aug 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
As the last uiSettings registered from the legacy world have been removed, this mixin is now unused and can safely be deleted.