I agree that around 4 or more function arguments, things start to become dicey.
I also agree that depending on situation, Ecto changesets might feel like an overkill.
Here’s a couple options below.
Keyword.validate! is a built-in way to ensure proper key names and you can even set defaults.
For doing a bit more validations, a good old recursive function that parses the keyword list key/value pairs is often enough. Or do it inline and even convert to a map right away (to later use the assertive map.field syntax):
Map.new(options, fn
{:host, host} when is_binary(host) -> {:host, host}
{:port, port} when is_integer(port) -> {:port, port}
end)
Beyond that, NimbleOptions — NimbleOptions v1.1.1 is a great option as it’s super easy to define basic validations, defaults, and it can ever create docs for you.
