FieldFormat registry - use new platform ui settings #46542
Merged
Conversation
This file contains 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
mattkime
changed the title
💔 Build Failed |
mattkime
force-pushed
the
FieldFormats_new-platform_uiSettings
branch
from
5a30eab to
aaf9f2a
Compare
💔 Build Failed |
💚 Build Succeeded |
|
Pinging @elastic/kibana-app-arch |
mattkime
added
the
release_note:skip
6 tasks
|
@elasticmachine update branch |
💚 Build Succeeded |
mattkime
added a commit
to mattkime/kibana
that referenced
this pull request
Sep 30, 2019
* use new platform ui settings
mattkime
added a commit
that referenced
this pull request
Sep 30, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
chrome.getUiSettingsClient();=>npStart.core.uiSettings;for the FieldFormatRegisteryChecklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers