finch

finch copied to clipboard

It would be nice to create list of high-priority tasks to compete until 1.0 release. We could discuss it's content and put our efforts to complete this list, stabilize client API and release v1.0.

I believe it would help to regulate finch needs and priorities, making it more mature in all terms.

---

• [x] Respond multiple content-types per coproduct endpoint (see #575, #583, and #794)
• [x] finch-generic, a standalone package providing generic derivation (see #528)
• [x] JSON streaming request (see #336, #557, and #812).
• [ ] Figure out whether or not to keep ValidationRule (see #513)
• [ ] Better API for io.finch.items (see #529)
• [x] Decode JSON directly from Buf (see #511)
• [ ] Better story for Encode.*[Exception] (see #547, Finch No Exceptions)
• [ ] ADT representing Endpoints metadata (see #581).
• [x] Reduce the performance gap between Finagle/Finch to 5%

Thanks @ImLiar! Here is my take on the roadmap: https://github.com/finagle/finch/wiki/Roadmap-1.0

Not so much things left to do, but there are two bold items we need to have a complete story in 1.0: streaming and type-level content-types. Otherwise, we're pretty ready for 1.0.

@vkostyukov nice to hear it! I'll do my best to move finch to v1.0 In the end, our team is kinda interested in stable API :smile:

Thanks @ImLiar! Appreciate your involvement!

I think, generally, the API is pretty settled for Endpoint. The only thin will change is everything around type-level content-type just because it's now written yet.