[GitHub] brooklyn-ui issue #69: Fix a couple issues with composer spec/config editor

[aledsage <gi...@git.apache.org>]

Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-ui/pull/69
  
    FYI without Alex's fix for the custom widget, editing the value behaves really strangely. Below is a description of the behaviour I saw without this fix.
    
    For example, for a dropdown widget, select a value (e.g. “t3.micro”), and then immediately clicking to view the yaml (or click “Deploy"), then the value is not included. However, if I choose the value and then click on another config field, then the value does take effect.
    
    Similarly if I try to type text in there, it goes weird. I had previously chosen “t3.micro” from the dropdown. I then clicked on the text box, deleted the text, and typed “foo”. When I then clicked on another field and then went to the yaml view, the value was “t3.mediu” (when it should have been "foo").
    
    With a new entity, clicking in the box and typing “foo” and then return, the yaml showed just “f”.
    
    Also, the validation error does not indicate the problem (that config is `constraint: [required]`)Instead, the error was only shown at the top-level Configuration.


---