bugfix: List editor behaves wrongly when calling setValue() more than once

[gerardobort]

It was accumulating elements on each call, apart of that, the render() method also wasn't refreshing the DOM after the first call.

The way to reproduce is simple..

// given an exisiting and already rendered form...
form.setValue({ a_list_propery: ['a', 'b'] });

The form was not only accumulating elements, but also not refreshing the view.

I hope this could reach the trunk,
Thanks,

[bpardee]

Same as #282

[philfreo]

this section seems unnecessary / not a common pattern in backbone-forms?

[gerardobort]

@philfreo I know... this is not a common pattern on this project, but also the List editor doesn't follow exactly the same pattern as the other editors.
Once you have inserted the form element into the DOM, a second call to listEditor.render() instead of updating the current element, will create a new one... this one new is not possible to trap or handle in any of the available events (there's no post-render trigger or something). So, this was the most viable solution I found =).

[rjmackay]

Just had the same issue described here. Could this get merged?

[alemangui]

+1

[exussum12]

Can you check the element has actually changed ? && old != new ?

[glenpike]

May have bearing on #517