Broken decoding of Issue without a body (when its a PR)
See original GitHub issueIssue Description
Issues endpoints also return PRs. Body in a PR is Option
, but isn’t in Issue
. This breaks at runtime during deserialisation.
github4s.GithubResponses$JsonParsingException: String: DownField(body)
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Fix encoding issue when source is encoded in utf8 ... - GitHub
Your fix obviously works for case 1. However, this is only a workaround for a broken web page. For cases 2+3 the manual...
Read more >Encoding/decoding model of communication - Wikipedia
The three positions of decoding proposed by Hall are based on the audience's conscious awareness of the intended meanings encoded into the text....
Read more >Analysis of Stuart Hall's Encoding/Decoding
Hall's essay challenges all three components of the mass communications model, arguing that (i) meaning is not simply fixed or determined by the ......
Read more >Encoding issue with Axios - Stack Overflow
My approach was this: Make the request with responseType and responseEncoding set as below. const response = await axios.request({ method: ...
Read more >Listen to Your Body: Decoding It's Warning Signals
Learn how to spot this dreaded disease by examining your early warning signs before cancer begins. Dream Recall – Not able to remember...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
🤔
Issues
is implemented using circe generic auto, maybe we could implement the decoders/encoders making them handle those casesCould filter out PRs from the issue endpoint, but it would cause unnecessary traffic. I’d be happy with an Optional body for now, since even in the docs they tell you to filter them yourself based on the presence of the pr urls field