AU2 - model get/set

So I am playing around with AU2 with a somewhat simple sudoku app and the cell model has some simple properties and validations/restrictions that I was using get/set for.

I then remembered that in AU1 using get/set was at one time not recommended because they had to be dirty checked.

I was wondering if there was the same recommendation for AU2? Does @computedfrom solve that issue for both?

Am I thinking of something else?

Au2 does smart tracking, it removed @computedFrom because it’s not needed.
Au2 does fallback to dirty-check if it cannot figure out dependencies, but most of the time dirty-check is not used.

If your binding on a getter doesn’t re-render as expected, fire a bug in github.

1 Like