Table state persisting in url

[ShootingStar91]

See if it is possible to save table state in url and load it when user comes back via previous-button or link. It's not necessary to yet implement all of these in a functional way, but to be sure that they can be implemented with the current table choice.

• [x] Column filters
• [x] Current page / page size
• [x] Sorting
• [x] Combination of these: If all of these have some setting, will the user see the same thing when coming back

[ShootingStar91]

Seems to work and is not too complicated.

However, since the table (at least by default) works by instantly updating the table after changes like one character is made to filter, it may not be sensible to save all the url changes to history. Also, because the history is the browsers history this might make the history a mess to navigate. Ask customers later when the feature is more fleshed out, if its ok not to persist the tables internal changes in history every time, but only the last state before going to another view or the individual item page.

[ShootingStar91]

The setting "autoResetPageIndex" had to be turned false. Otherwise it would always reset pageIndex to 0 on first render, after reloading state from url. It works now, but it's not known if this will end up having adverse effects: documentation said that this setting prevents user being shown empty pages on certain changes, I did not get this by testing but it could happen.