You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the first time you 'get' the sorted property while the property itself is null, then the sorted property is never recalculated if the property receives a value afterwards (see attached file for a reproduction scenario).
works on 2.15.3, but fails on 2.16.0
The reason why this fails in our app, is that property is a sub-property of model (model.users and model.sortedUsers) and that rendering starts between the beforeModel and model hook. So, the value controller.model is still null. sorting.zip
The text was updated successfully, but these errors were encountered:
If the first time you 'get' the sorted property while the property itself is null, then the sorted property is never recalculated if the property receives a value afterwards (see attached file for a reproduction scenario).
works on 2.15.3, but fails on 2.16.0
The reason why this fails in our app, is that property is a sub-property of model (model.users and model.sortedUsers) and that rendering starts between the beforeModel and model hook. So, the value controller.model is still null.
sorting.zip
The text was updated successfully, but these errors were encountered: