fabiocarvalho777

By the way, regarding how to implement this, I was thinking about providing a subclass of `DeclarativeContract`. That would be also nice in terms of backwards compatibility. Let me know...

Hello Marvin, Your ZERO body example is right, that is what we mean. The problem with it is that with a method like the one in the example, Feign skips...

The only problem with using the map for the body object(s) is that the parameter name [is not always necessarily known](https://docs.oracle.com/javase/8/docs/api/java/lang/reflect/Parameter.html#getName--). And knowing the name of the parameter is important....

The map for the body object would only work if the key of the map is an integer (the order of the parameter), so, knowing that, we can get from...

Here is an example of what we are trying to achieve: ``` java @Query List getBooks(@Variable("authorId") int authorId, @Variable("offset") int offset, @Variable("limit") int limit); ``` In this example `@Query` is...

> But, there is a big risk of breaking existing encoders left and right... That is why I suggested that we could create a new type of `Contract` (extending `DeclarativeContract`,...

Hello, Thanks @velo and @kdavisk6 for taking the time to look at this!! We appreciate it! The recommened solution looks promissing and makes sense to me. There is just one...

> > ```java > > void encode(Object[] arguments, RequestTemplate template); > > ``` > > That would totally break `Encoder` backwards compatibility @velo Only if we are modifying the original...

> The template should be resolved by then so you can access the values using the query and header methods on Request Template. I’ll verify. If not, it’s simple to...

> @fabiocarvalho777 when you propose `Object[] arguments`, would that be a copy of all arguments for a given method? > > so, if I have > `void removeCall(@Header String arg1,...