John Cowen 9013e53ebc ui: Ensures nested policy forms are reset properly (#5838) ... 1. All {{ivy-codemirror}} components need 'refreshing' when they become visible via our own `didAppear` method on the `{{code-editor}}` component (also see:) - https://github.com/hashicorp/consul/pull/4190#discussion_r193270223 - 73db111db8 (r225264296) 2. On initial investigation, it looks like the component we are using for the code editor doesn't distinguish between setting its `value` programatically and a `keyup` event, i.e. an interaction from the user. We currently pretend that whenever its `value` changes, it is a `keyup` event. This means that when we reset the `value` to `""` programmatically for form resetting purposes, a 'pretend keyup' event would also be fired, which would in turn kick off the validation, which would fail and show an error message for empty values in other fields of the form - something that is perfectly valid if you haven't typed anything yet. We solved this by checking for `isPristine` on fields that are allowed to be empty before you have typed anything.		2019-06-04 15:57:35 +01:00
..
add-existing-steps.js	UI: ACL Roles (#5635)	2019-05-01 18:22:37 +00:00
add-new-steps.js	UI: ACL Roles (#5635)	2019-05-01 18:22:37 +00:00
list-steps.js	UI: ACL Roles (#5635)	2019-05-01 18:22:37 +00:00
remove-steps.js	UI: ACL Roles (#5635)	2019-05-01 18:22:37 +00:00
reset-steps.js	ui: Ensures nested policy forms are reset properly (#5838)	2019-06-04 15:57:35 +01:00