v1.0 Roadmap

[sergeykolbasov]

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.

---

• Respond multiple content-types per coproduct endpoint (see Support multiple content-types per service #575, Introduce ServiceBuilder #583, and Introduce Bootstrap #794)
• finch-generic, a standalone package providing generic derivation (see Add new package finch-generic #528)
• JSON streaming request (see Provide codecs that support streaming #336, Add module for streaming with iteratees [WIP] #557, and Request streaming support through circe-streaming #812).
• Figure out whether or not to keep ValidationRule (see Replace ValidationRule with Cat's Validated #513)
• Better API for io.finch.items (see Refactor io.finch.items #529)
• Decode JSON directly from Buf (see Eliminate meaningless to-string conversion #511)
• Better story for Encode.*[Exception] (see Figure out why Encode[Exception] is often not picked up #547, Finch No Exceptions)
• ADT representing Endpoints metadata (see ADT for Endpoint metadata #581).
• Reduce the performance gap between Finagle/Finch to 5%

[vkostyukov]

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.

[sergeykolbasov]

@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 😄

[vkostyukov]

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.