-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing bug in implementation of makeSome without repeting fresh layers #8850
base: series/2.x
Are you sure you want to change the base?
Conversation
@ghostdogpr Would you mind taking a look? Do you think the testing is enough or are there some other use cases that you think should be covered? The |
When I get time, I will try to test that one on my work codebase. Would be nice if others did too @kyri-petrou maybe? |
I am getting false positive warnings like this:
when doing type BaseDependencies = Config with TransactorForCK
trait TransactorForCK { def transactor: Transactor[Task] }
ZLayer.makeSome[BaseDependencies, SomeService] where I am not supplying |
I am not able to create a similar warning. Are there other type of incorrect warnings or are all the same? Would you mind giving a minimal example or some more information? The layers and its
|
It's a little tricky to minimize but I was able to reproduce with this configuration: trait B
val reproducer = ZLayer.makeSome[B, Reproducer.A](Reproducer.live) In another file: object Reproducer {
case class A()
val live: ZLayer[B, Nothing, A] = ???
} Both are under different packages. If I put them together it seems to work. |
Reimplements #8678 fixing #8767 and adds new tests with different combination of layers to check behaviour.