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 you implement overscanIndicesGetter, it gets called twice on every scroll event. Once to get the horizontal value and again to get the vertical value. However, nothing is passed in to let us know which of these it is. If we want to return different values for horizontal vs vertical scrolling, it isn't possible.
Good observation. I probably prefer direction: 'vertical' | 'horizontal' but I don't feel strongly. Since this would be a backwards compatible change, I'd be happy to accept a PR for it.
I'll do this. One additional thing to consider. When using a List, the overscanIndexGetter is being called for both Horizontal and Vertical, even though there is no horizontal. Should I also optimize this away so that Lists don't ask the overscanner for horizontal?
If you implement
overscanIndicesGetter
, it gets called twice on every scroll event. Once to get the horizontal value and again to get the vertical value. However, nothing is passed in to let us know which of these it is. If we want to return different values for horizontal vs vertical scrolling, it isn't possible.This is what the code is
I propose passing another value for horiz/vertical scrolling. Something like this:
What do you think?
The text was updated successfully, but these errors were encountered: