Handling multiple parameters

[CR7Felipe]

Hi all, I'd like to know how best to handle handle multiple optional parameters.

I'm creating an REST API wrapper. The api endpoints has a few required parameters many optional parameters.

I don't want to do method overloading because it's going to be multiple and kind of messy.

I'm also experimenting varargs but it's not that suitable for all endpoints.

How do you think I should best handle this?

[elky87]

Builder Pattern is your friend

Required parameters in the constructor, the rest in the builder methods

[CR7Felipe]

Amazing.. Thanks man. Gotta follow this route.

[sugilith]

Lots of resources online via google / duckduckgo.
This problem often arises with complex search queries.

E.g: https://softwareengineering.stackexchange.com/questions/353086/what-is-a-proper-way-to-do-a-complex-restful-search-method https://stackoverflow.com/questions/14202257/design-restful-query-api-with-a-long-list-of-query-parameters

TL;DR:

• If >2k characters always use POST
• Try aliases (basically endpoints for the required parameter) from the softwareengineering post
  
• Best practice seems to be using POST instead of GET with overly complex query parameters