angular-ui/ui-grid

infinite scroll dataRemovedTop() and dataRemovedBottom() broken

Open

#4,904 建立於 2015年12月24日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)JavaScript (5,395 star) (2,496 fork)batch import
grid-infinite-scrollhelp wantedseverity: memory leakseverity: performance

描述

I'm using version 3.0.7 and Chrome browser Version 47.0.2526.106 (64-bit) for Mac OS X.

I was having problems with my own code. Whenever I try to 'trim' my in-memory grid data by calling dataRemovedTop() or dataRemovedBottom() a needLoadMoreDataTop data is always triggered.

However, then I took the example/demo code from the ui-grid.info site here: http://ui-grid.info/docs/#/tutorial/212_infinite_scroll and played with it and noticed the same issue was happening.

'trimming' data does not currently work properly.

Please let me know if you need anymore data points.

貢獻者指南

技術棧
javascriptangularhtmlcss
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
AngularJSUI Grid basicsJavaScript
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Reproduce the bug using the infinite scroll demo at http://ui grid.info/docs/#/tutorial/212 infinite scroll. Examine the grid data methods such as dataRemovedTop() and dataRemovedBottom() in the ui grid source code, likely in the grid controller or data service. Look for any recent commits or PRs mentioning this issue. The goal is to understand why trimming triggers needLoadMoreDataTop incorrectly and propose a fix.