-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Cases] Custom field default values in configuration forms (#174628)
See #171747 for more info ## Summary **Merging into a feature branch.** This PR handles **only** the cases configuration page. With these changes, users can now configure default values for custom fields in the UI. <details><summary>Text custom field</summary> <img width="1728" alt="Screenshot 2024-01-12 at 13 56 58" src="https://github.com/elastic/kibana/assets/1533137/972ee7b4-e5a3-4368-a499-914bde7f0bc1"> </details> <details><summary>Toggle custom field</summary> <img width="1728" alt="Screenshot 2024-01-12 at 14 01 43" src="https://github.com/elastic/kibana/assets/1533137/5b8a1e0c-7d90-4f51-a107-ad989af645f3"> </details> When clicking `required` the default value for a `toggle` custom field is `false`. When clicking `required` the default value for a `text` custom field is an empty `string`. <details><summary>Trying to save an empty `string` as the default value of a `text` custom field should display an error message on the form.</summary> <img width="1728" alt="Screenshot 2024-01-12 at 14 00 39" src="https://github.com/elastic/kibana/assets/1533137/e5925d15-801e-4da2-87ef-d4d6686290f4"></details> Viewing previously created custom fields should display their default values correctly. Viewing previously created custom fields **in a version where default values did not exist** should display the forms correctly. ## Other Notes 1. I changed the property name from `default_value` to `defaultValue` 2. I fixed some instances of `expect(screen.getById...` where I found them. 3. I addressed most comments left [from the previous PR](#174043). The last one will be a separate PR(moving some types around).
- Loading branch information
Showing
46 changed files
with
641 additions
and
336 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.