Adam Warski

Better error messages

2

This is probably a large issue, with multiple improvements that can be done. For example, when removing the `given Print[Int] = _.toString` from the readme example, the error message is:...

Consider not using Mirrors for derivation, so that multi-level hierarchies can be suppored

4

Mirrors give us a lot "for free", but I think we could do just as well without them (that is, give the same user experience & performance), while additionally supporting...

For sure this includes union types and opaque types.

.modify doesn't work on parametrised types

1

``` case class Test[T](a: T, b: Int) Test("1", 1).modify(_.b).setTo(10) ```

Extend cats-autowire to handle any effect type

20

Currently autowire works only for `IO`. It would be great if it would: (a) work for any `F[_]` (b) verify (if at all possible?) that all passed effects/factories/resources use the...

"value x$2" when wiring a parametrised type

5

Using `PrometheusMetrics[IO]` as a dependency causes problems when compiling bootzooka: ``` [error] Error while emitting Dependencies.scala [error] value x$2 [error] one error found ``` As a work-around, the dependency is...

Sometimes if you forget to add a dependency to autowire's parameters which needs manual creation you get errors such as a missing `String` dependency (if a `String` is needed to...

So that the jar and sbt dependency are more readable, e.g. `macros-auto-cats`

Don't autowire no-arg constructors, or make this configurable?

1

Citing @mbore: > Actually I'm still not sure if we want to support no parameters constructors. It may cause difficult to debug mistakes like "forgot to pass filled config", for...

autozio! :) We should return a `ZManaged` as the result.