Why you don't you use Pageable in your controller ?
Pageable can handle many sort queries, each of them will be stored in orders list. Moreover, any of pageable parameters aren't required. When you don't pass them in url, pageable will contains default values (page = 0, size = 20). You can change default values by using @PageableDefault annotation.
GET .../test?sort=name,desc&sort=code,desc 
Why you don't use Pageable in your controller ?
Pageable can handle many sort queries, each of them will be stored in orders list. Moreover, any of pageable parameters aren't required. When you don't pass them in url, pageable will contains default values (page = 0, size = 20). You can change default values by using @PageableDefault annotation.
GET .../test?sort=name,desc&sort=code,desc
Why don't you use Pageable in your controller ?
Pageable can handle many sort queries, each of them will be stored in orders list. Moreover, any of pageable parameters aren't required. When you don't pass them in url, pageable will contains default values (page = 0, size = 20). You can change default values by using @PageableDefault annotation.
GET .../test?sort=name,desc&sort=code,desc
Why you don't use Pageable in your controller ?
Pageable can handle many sort queries, each of them will be stored in orders list. Moreover, any of pageable parameters aren't required. When you don't pass them in url, pageable will contains default values (page = 0, size = 20). You can change default values by using @PageableDefault annotation.
GET .../test?sort=name,desc&sort=code,desc
