Each parameter what all know, why do you want to pass twice? To modify the mass participation in?
This is the same Datatable, the parameter is much more concise
CodePudding user response:
Either change request header content-type as json, or put your object into a string, or don't get so deep level
CodePudding user response:
reference 1st floor nian_cj response: or change request header content-type as json, or put your object into a string, or don't get so deep hierarchy the first picture is the original, I only change the url, I don't know why the back end so many parameters, the second is the bosses to turn, but I don't know what changed CodePudding user response:
refer to the second floor is the shrewd response: Quote: refer to 1st floor nian_cj response: Either change request header content-type as json, or put your object into a string, or don't get so deep hierarchy the first picture is the original, I only change the url, I don't know why the back end so many parameters, the second is the bosses to turn, but I don't know what changed Weed out those who don't, you used to the deep level of object into a simple single object For example: the old object { The dataTable: { Pagination: { Page: 1, Perpage: 10, } } } New object: { Page: 1, Perpage: 10, } CodePudding user response:
reference nian_cj reply: 3/f Quote: refer to the second floor is the shrewd response: Quote: refer to 1st floor nian_cj response: Either change request header content-type as json, or put your object into a string, or don't get so deep hierarchy the first picture is the original, I only change the url, I don't know why the back end so many parameters, the second is the bosses to turn, but I don't know what changed Weed out those who don't, you used to the deep level of object into a simple single object For example: the old object { The dataTable: { Pagination: { Page: 1, Perpage: 10, } } } New object: { Page: 1, Perpage: 10, } Write on these parameters