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
So in controller I was accessing it through this.adapter since controller was assigned to vm variable.
Now it's available through $scope.$parent.vm.adapter.
the original intention for the adapter access was to look it up starting from the scope associated with the viewport - this is how all other attributes work. As I was working on implementation of the adapter on controller syntax I discovered that for adapter only the lookup point is the scope associated with the scroller itself. So yes, I considered it to be a bug and fixed it to implement the expected behavior. I think in your situation it would be best to use the adapter on controller syntax
After update to version 1.5.1 all adapter assignments are no longer working for me.
So in controller I was accessing it through
this.adapter
since controller was assigned to vm variable.Now it's available through
$scope.$parent.vm.adapter
.Is that expected behavior?
Is this commit causing it?
8c714d5#diff-acd620d807e19ec97ee631f9cb480854
The text was updated successfully, but these errors were encountered: