palantir / palantir/conjure-java-runtime
Endpoint returning Alias of optional<T> + Http 204 results in NeverReturnNullDecoder exception
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 95
- Forks
- 96
- Avg merge
- 3h 38m
- Merged PRs (30d)
- 33
Description
What happened?
An internal service has legacy, non-conjurized, endpoints that return null which breaks with the NeverNullDecoder being added as a default. We're pretty low in the stack so major releasing just to address this break is not a feasible option for us. This will prevent us from taking all future updates.
What did you want to happen?
Either remove it completely or make the NeverNullDecoder optional.
Contributor guide
No contributing guide indexed for this repository
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 NeverNullDecoder behavior described for Optional responses and HTTP 204, then reproduce the legacy endpoint case that returns null. Review the surrounding decoder configuration and existing coverage, if present; done means the decoder behavior is optional or removed and the reported response no longer raises NeverReturnNullDecoder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100