Closed Arnedeklerk closed 1 year ago
I don't see how the API is related to this. The Js table component should take the initial table (whatever it is and in whichever order) and it should render/visualise more lines as the user scrolls.
I don't see how the API is related to this. The Js table component should take the initial table (whatever it is and in whichever order) and it should render/visualise more lines as the user scrolls.
Ah shoot. You're right. Apologies my brain is fried after today 😄
Happy and closing
Part 1 of 3. See 2 here.
Currently, the Gene and Evidence views in KnetMiner display a limited number of rows based on the bottom left selector, which forces the user to choose how many rows to display. This can lead to excessive scrolling or limited visibility of the available data (or worse, the app to freeze in a user's attempt to find a particular evidence!).
Thus: infinite scrolling for both Gene and Evidence views. This feature would initially render only the first 50 (or fewer) genes/evidences, and as the user scrolls, the frontend would add the next batch to the list, allowing seamless access to all available data without manual intervention.
To achieve this, the following changes are required (@marco-brandizi to confirm please):