Lawrence Lavigne

POC PR (work in progress): #632

Agreed with @noelmarkham that we shouldn't rely on implicits where we might need different implementations for two or more methods with the same signature, which is a reasonable thing for...

@noelmarkham @fedefernandez Please have a look at https://github.com/higherkindness/mu/commit/1f9d477f7f9558d4b1f70bf69684f899dd7131a6. Note that it's a _very_ crude approach as I had to use `Option` parameters defaulting to `None` just to get it working...

BTW, not sure why the new localhost server test is passing locally and falling in CI - just saw that the previous version with implicits had the same problem. In...

@noelmarkham Agreed, there's a risk this could end up over-engineered. I think it comes down to whether we need to allow arbitrary code in the user customization or not. If...

Thanks Noel! Naming the annotation `@http4s` seems a bit unusual but I can see it justified as that shows the annotation to be a pass-through to that specific library. Just...

For reference, here are the corresponding issues for `avrohugger` which is our implementation for Avro-schema sourcegen: Schema downloads: https://github.com/julianpeeters/sbt-avrohugger/issues/26 Schema uploads: https://github.com/julianpeeters/sbt-avrohugger/issues/27 (most of the discussion and code samples are...

This sbt plugin could also be useful: https://github.com/iadvize/sbt-avro

Quick note - regardless of API used, the Schema Registry only supports `.avsc` files which are individual class definitions (our `@message` classes). Some of our users have `.avdl` or `.avpr`...

Creating special records to represent RPC calls is an interesting idea! We could do this with a single record I think, and using the actual message record types as req/resp...