Don't create redundant `Ref` in the `Client#fromHttpApp`
See original GitHub issueThis is a follow-up from https://github.com/http4s/http4s/pull/6325.
Ross made a proposal that we can don’t create Ref
in a case when the request/response body isn’t streaming.
One should keep in mind, that a single Ref
instance is reusing.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
No way to omit redundant ID parameter on generated PUT methods ...
In my example, the Name property is already there, it's just duplicated between the body and the path in the REST API (and...
Read more >In general, would it be redundant to have two GET routes for ...
GET /api/users?username=GuiMendel HTTP/x.y ... These identify different resources; the two resources don't have to have any meaningful ...
Read more >GraphQL `createDiffNote` forces clients to compute redundant ...
The API requires the client to send (and often compute) redundant information that is available in the API. I believe this is the...
Read more >Best practices for REST API design - Stack Overflow Blog
Learn how to design REST APIs to be easy to understand for anyone, future-proof, secure, and fast since they serve data to clients...
Read more >15 fundamental tips on REST API design | by Williams O
Therefore, it's very important to design REST APIs properly so that we don't run into problems down the road. Creating an API from...
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 FreeTop 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
Top GitHub Comments
Currently, no one is working on this issue, so it’s up to you exactly 👍🏻
That’s wonderful, thank you!