Remote mode : Page is set to 1 when I reset a filter

I have a table that I use in remote mode.

If I set the properties like this :

data = <a list of 2 elements>
sizePerPage = 5
options.page = 2
fetchInfo.dataTotalSize=7

then it works fine. I see my two elements, and the page number 2 is highlighted.

But when I set a text filter to blank, or a custom filter to blank (I call filterHandler() with no parameters inside my custom filter), then the page 1 becomes highlighted in pagination list, and I can’t click on it or page 2. The props haven’t changed, so I see a mismatch between props.options.page=2 and state.currPage=1.

Do you have a workaround or a fix? I think this is the last bug left in my list and I’m a little bit frustrated ^^

Thanks in advance, and great work with this component, it’s very useful.

[BenoitAverty]

Sorry, I wasn’t very clear because I just wrote all my findings in the same post. I’ll try to focus on the essential:

• When a filter changes, the page becomes 1. This makes sense for the table in normal mode because the data changes.
• In remote mode, this is problematic because it causes a mismatch between the page that’s in the table state, and the page that’s in the props.options object. The result is that clicking on the page links doesn’t work anymore. I think the reset should be made to options.page instead of the first page index (if it’s specified).
• Another problem if that the page is reset to one even if the data/filter doesn’t change. For example, if the filter was already empty and it calls the handler again, then the page is reset to one even though nothing has changed. If the filter was set but has no effect, It also goes back to page one even though the data doesn’t change, which is counter intuitive inmy opinion.

I hope it’s more clear, don’t hesitate to ask if something isn’t clear

[BenoitAverty]

No problem, Do it when it’s convenient 😃