Do we always have to use "path" in get services?

[bizonKiller]

Hi in previous version for GET pokemon/{name}/{version} we could use getPokemon(name, version). Now from what I see we have to use getPokemon( {path: { name: "aa", version: 1 }})` or something similar.
Am I missing something?

[mrlubos]

@bizonKiller you're not missing anything, that sounds correct!

[bizonKiller]

I highly respect your work so I want do to give you some feedback of new user testing lib and deciding not to use it.
In my opinion exposing path params as function params make it is easier to use and hide most of the underneath complexity. Additionaly the type of the parameter like Options<GetPokemonData, false> is not easy to understand.
If you compare something like axios.get(\pokemon\${name}\${version})
and getPokemon( {path: { name: "aa", version: 1 }} you get nice strong typing but it is easier to understand axios.
I want junior developer to use services efficiently without additional thinking and understanding engine of lirary.

[mrlubos]

Appreciate the feedback! I would be open to supporting alternative syntax for clients, however, that represents a significant lift. Then there are questions around handling duplicates, order of arguments, etc. This was one of the first changes I've made when I started working on this package -> https://heyapi.vercel.app/openapi-ts/migrating.html#v0-27-38. Do you already have a solution in mind that you're planning to use? I could have a look at how they solve these challenges