Ryan Plessner

@joroKr21 You can push a commit that removes the `-SNAPSHOT` from the version in version.sbt and CI will handle the rest. Something like this should work: https://github.com/finagle/finch/commit/9b18fb743fa62abc1fff74452133a9c93fb22567

I really like this as a type param per-endpoint. re: `more flexible, but has to be repeated` I'd be curious to hear how common having multiple `serve`s is. My suspicion...

> allows us to use a more consistent approach for configuration. This is a good point. And thinking more on my suspicion that its not called many times then it...

I've been thinking about this one for awhile and fiddling with some code. You're right, its a lot of work. My impressions so far: - From what I've seen the...

Ah, now I understand. That sounds like a solid approach. I'm interested to see what you come up with.

@aroberts, I don't think it this has been abandoned (not sure it ever made it passed the idea phase). I've been thinking about it a lot recently because we started...

I've been playing with an implementation of `Endpoint.Meta` and I see it working as a replacement for `RequestItems`, but I'm not quite sure about `Error.Source`. Was there some more modeling...

This is because the published documentation is still for the the `finch` artifacts. The focus of the next release is documenting and cutting over the `finchx` artifacts into the mainline...

I started a [branch](https://github.com/rpless/finch/tree/rpless/endpoint-meta) to implement this a few weeks back (sorry I probably should have mentioned it). I based it on [the previous comment](https://github.com/finagle/finch/issues/581#issuecomment-243887768) Hopefully I'll have some time...

Not quite (although twitter-server does use it a lot), Finagle uses jackson for ToggleMaps (which does get loaded by finagle-http). Finch does not use it directly so pinning to the...