[management] Adjustments to Settings components and utilities#166413
[management] Adjustments to Settings components and utilities#166413clintandrewhall merged 3 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
|
Pinging @elastic/appex-sharedux (Team:SharedUX) |
8dfec61 to
eccf55f
Compare
ElenaStoeva
left a comment
There was a problem hiding this comment.
Thank you for making these fixes and additions @clintandrewhall! Overall LGTM.
I only noticed some strange behaviour in the image field but I think some of it exists from before this PR. Approving the PR since these issues could be addressed in a separate one; plus, there are no image settings in serverless.
90120ba to
cdb51c2
Compare
cdb51c2 to
f9c5b38
Compare
vadimkibana
left a comment
There was a problem hiding this comment.
Codeowners changes LGTM
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Public APIs missing comments
Unknown metric groupsAPI count
History
To update your PR or re-run it, just comment with: |
Summary
While working on #166319 I found a number of bugs when working against actual UI settings stored in Kibana. This PR addresses those issues without waiting for the Settings page to be complete:
inputcomponents to have cleaner APIs, includingunsavedChangeandfield"all the way down".normalizeSettingsfunction.UiSettingsServicein an actual deployment of Kibana are drastically unpredictable. In some cases,typeis missing, butvalueis there... orvalueis missing entirely, but auserValueis there.onChangeFnto acceptundefinedto indicate an unsaved change has been reverted, rather than relying on the value in the unsaved change.unsavedChangeprop to be undefined, (to indicate the lack of an unsaved change), rather than an undefined value.ImageFieldInputwasn't removing a file that had been set when resetting to default;FieldInputcomponents to reset a field's input beyond resetting the value, (if necessary).commonsetups to allow for changes to theonChangetypes.FieldRowwas indexing an unsaved change byname, rather than byid.query.settingsandfields.