Closed notmessenger closed 8 years ago
https://github.com/ember-forge/ember-forge-ui/commit/d513da0516e4d7c4d3a1f85e33db56f11667c5d3 extracted the previous commit into a mixin.
https://github.com/ember-forge/ember-forge-ui-bootstrap4/commit/1a741b667a763464eb2aa2d31d319305df4f7d87 experiences this problem as well.
This was introduced by https://github.com/ember-forge/ember-forge-ui/commit/1beda3fabf0455ef15bc8cedca13b9134dc07a77 which is the commit that ties the existence of error to error state on associated element. This error comes to be when the data on the
errors
object is modified. It's because of thebinding but I have not yet figured out what exactly is causing it, as the logic that updates the
errorState
property -updateErrorState()
is not being called more than once.