Improve the ergonomics of Endpoint#implement

[kitlangton]

Currently, implement must be passed a handler, which itself requires a function whose input matches the input of the endpoint. It's also necessary to manually ascribe a type to the handler's input parameter.

  val httpApp = Endpoint(Method.POST / "books").in[BookProps].out[Book]
    .implement(handler { (props: BookProps) => // <-- We must ascribe a type to the input parameter
      BookService.create(props)
    })

In ZIO land, we don't love manually ascribing types when they can be inferred from the context. Ideally, one could write the following:

  val httpApp = Endpoint(Method.POST / "books").in[BookProps].out[Book]
    .implement { props => BookService.create(props) }

As the Endpoint already knows its own input type, it can constrain the provided function to be of the right type. The user's IDE will know exactly what input is required, rather than forcing the user to provide a handler with a logically redundant + manual type ascription. Further, it would be great if implement built the handler internally, as it's just extra syntactic noise.

[jdegoes]

/bounty $100

[algora-pbc]

💎 $100 bounty • ZIO

Steps to solve:

1. Start working: Comment /attempt #2811 with your implementation plan
2. Submit work: Create a pull request including /claim #2811 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to zio/zio-http!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @987Nabil		#2894

[algora-pbc]

💡 @987Nabil submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[algora-pbc]

🎉🎈 @987Nabil has been awarded $100! 🎈🎊

• Share on socials
• Give feedback