Whether the paging of the list and Filter in admin should be linked to routing.

in common scenarios in the background of administrators, the data is listed in table, paged and conditionally searched.
previously made an admin that is written by react, so it doesn"t matter if all the data are obtained asynchronously.
but now you need to ReFactor an old admin project (also known as the react technology stack) and find that their paging and search will push the route and then retrieve the data, and then retrieve the data when the route returns to (pop). I wonder if this is necessary?


maybe the company has special needs and needs to reproduce the query conditions on url. When sending url to others, the filter results are the same as those you see


no problem.
listens for routing changes.
then load the required data.


is not necessary. The practice of
is also unreasonable, so it is recommended to search directly.


has done similar things, mainly filtering.


look at the requirements. Both methods have

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1bea5be-319f8.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1bea5be-319f8.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?