Kevin Davis
Kevin Davis
Please upgrade Feign. This has been corrected.
@d0x In this situation, you may be able to use a custom Parameter Expander to resolve the value. For example: ```java public interface MyClient { @RequestLine("GET /") @Headers("Codec-Header: {codec}") Object...
@amolsolanke From the error, it looks like Spring's message converter is not a `Refresh` candidate. I recommend asking on Stack Overflow about how to enable that capability in Spring. That...
I've built something like this in `feignx` already. I rely on the `Expander` concept. Maybe we could consider the same here. We could register an `Expander` without having to tie...
The more I think about this, the more I like the idea of expanding `@Param` to be used at the method and class level. Here's an example: ```java @Param(value =...
> Problem is if `EnvironmentExpander` needs to read some configuration from a database or need some other classes access.... > > Let's say I have a client that I authenticate...
Agreed. I was confusing Expander with something I've been working on in `feignx`. We can add a `supplier` to the annotation too. ```java @Target({ElementType.PARAMETER, ElementType.TYPE, ElementType.METHOD}) @Retention(RetentionPolicy.RUNTIME) @Documented public @interface...
> I don't see any point on having the `@Param` if we include this on the builder. > > Am I missing something? I'm looking towards the annotation processor, but...
Your literal is in the format of an expression. To use this you must pct-encode the start and end braces using `%7B` and `%7D%` to bypass expression handling. See https://tools.ietf.org/html/rfc6570#section-2.2...
@dumaswong At the moment, you are correct. `HeaderTemplate` does not have any built in JSON support. My recommendation is to use an expression and pass in the JSON value as...