Feature description
When advanced filtering is disabled, you handle the filter directly in the use table hook, so there is no need for json encoding/decoding involved and a cleaner looking url with nuqs is generated.
could you also implement this behavior for the sorting, so that no json encode/decode is neccessary?
for example:
current: https://tablecn.com/?status=in-progress&sort=[{%22id%22:%22createdAt%22,%22desc%22:false}]
without json: https://tablecn.com/?status=in-progress&sort=createdAt,asc
also it would be a valid syntax, when the same search parameter is given multiple times:
current: https://tablecn.com/?status=in-progress&sort=[{%22id%22:%22createdAt%22,%22desc%22:false},{%22id%22:%22title%22,%22desc%22:true}]
without json: https://tablecn.com/?status=in-progress&sort=createdAt,asc&sort=title,desc
Additional Context
Additional details here...
Before submitting
Feature description
When advanced filtering is disabled, you handle the filter directly in the use table hook, so there is no need for json encoding/decoding involved and a cleaner looking url with nuqs is generated.
could you also implement this behavior for the sorting, so that no json encode/decode is neccessary?
for example:
current:
https://tablecn.com/?status=in-progress&sort=[{%22id%22:%22createdAt%22,%22desc%22:false}]without json:
https://tablecn.com/?status=in-progress&sort=createdAt,ascalso it would be a valid syntax, when the same search parameter is given multiple times:
current:
https://tablecn.com/?status=in-progress&sort=[{%22id%22:%22createdAt%22,%22desc%22:false},{%22id%22:%22title%22,%22desc%22:true}]without json:
https://tablecn.com/?status=in-progress&sort=createdAt,asc&sort=title,descAdditional Context
Additional details here...
Before submitting