Created attachment 1683317 [details]
Short term UX design
Description of problem:
When using the new form/YAML switching interaction (new for 4.4/4.5) for creating and editing operator custom resources, the user can enter incorrectly formed YAML in the YAML editor and is not notified that upon switching to the form editor, this data is lost. Ideally we'd highlight in the editor that the YAML is malformed, but we should at least warn the user on switching to the form editor that this malformed YAML will be lost (ideally with the line number of the malformed YAML if possible.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a new operator custom resource (operand) and enter malformed YAML in the YAML editor
2.Switch to the form editor
3.Switch back to the YAML editor.
The malformed YAML is no longer present upon switching back to the YAML editor.
The user should have been warned when switching away from the YAML editor initially that the malformed YAML will be lost, so they can review the YAML or be aware of its removal.
Discussed solution with Ben P and Jon J, maybe we just do attached design for now with intent to enhance in 4.6.
There is a fix pending for this, but the PR can't be opened until https://github.com/openshift/console/pull/5237 merges
Created attachment 1688795 [details]
Latest version is as the design now. (refer to the the screenshot from attachment)
Verified on 4.5.0-0.nightly-2020-05-15-011814
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.