template has not been resolved
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.8k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 41
Description
Tenho a seguinte assinatura de método:
@RequestLine("POST /get-contracts?gw-app-key={token}")
@Headers({ "Content-Type: application/json" })
ContractsFinResponse getContracts(@Param("token") String token, ContractClientRequest contractClientRequest);
O request é executado com sucesso utilizando a versão 9.7.0
Ao atualizar para a versão 10.4.0 o request para a dar um encodeException, retornando template has not been resolved.
O que teria que estar alterando para poder mudar para a versão 10.4?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the annotated getContracts method in the issue and reproduce the request using Feign 9.7.0 and 10.4.0. Compare template resolution and parameter handling around the POST request, then verify that the migration path avoids the “template has not been resolved” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100