Make sure render can be called after a value has been updated

[exussum12]

relates to #361. Added some tests. All passing on Chrome and Firefox, Not tested others

[philfreo]

@exussum12 can you see if list.js (in extra/) needs a similar update? There are some other PRs (e.g. #372) doing similar things and it'd be nice to take care of all these setValue changes at once if they're necessary.

[exussum12]

Listy looks ok to me, All of its set values seem to update the model too

[Blasz]

So this PR was never landed?

[exussum12]

No. Sorry I accidently deleted the branch and then re opened the pull request. I've been using the code here for about a year and as far as I can sss its ok

[exussum12]

Oops didn't re open. I will re open after I push the branch

[exussum12]

Branch is back

[powmedia]

Thanks @exussum12

[Blasz]

Awesome.

[fonji]

👍

[Blasz]

What's the policy on when the distribution folders should be updated. Only on tagged version releases or should they be rebuilt with/after pull requests as well?

[philfreo]

Just update src here -- distribution will get auto-built once it's merged in. I haven't had a chance to look at this yet but maybe @powmedia has.

@exussum12 does the test I wrote in #378 (comment) pass in this branch?