I've an enhancement on the pagination request you could use the one based index instead of subtracting to be zero by just providing the property on the application propertise spring: data: web: pageable: one-indexed-parameters: true
Can i do a post for getting things if i have a nested hierarchy like a category inside multiple categories, then brand inside multiple brands, then size where I'll be having lot of sizes. So if i want to pass multiple categories, brands, and sizes to get info
REST principles are more of guidelines than rules. Sometimes we have to use POST for getting the information due to the payload limitation of GET request. For example Elasticsearch uses POST for fetching matching documents.
Thank you so much.
Amazing thank you brother !!
Thank you si a for the wonderful effort
good content, thank you
Useful tutorial things!
It would be amazing as well if you did best practice one with a similar great explanation
Only the first topic covers "Rest". Url naming patterns and certain status codes are not mandatory to be restful. Only a uniform interface.
production-ready is also highly claimed too --> hence reworded as is the DONE #productEconomy scale ready
I've an enhancement on the pagination request you could use the
one based index instead of subtracting to be zero by just providing the property on the application propertise
spring:
data:
web:
pageable:
one-indexed-parameters: true
Sir, kindly make the tutorial over Servlet JSP JDBC so that our prerequisites are clear.
Can i do a post for getting things if i have a nested hierarchy like a category inside multiple categories, then brand inside multiple brands, then size where I'll be having lot of sizes. So if i want to pass multiple categories, brands, and sizes to get info
REST principles are more of guidelines than rules. Sometimes we have to use POST for getting the information due to the payload limitation of GET request. For example Elasticsearch uses POST for fetching matching documents.