This regards the problem I first mentioned here yesterday: https://elixirforum.com/t/protocolex-extended-protocol-library-using-matchers/6822/10
I use ProtocolEx extensively, so it's all over my (umbrella) project, both in the domain and the web apps. The issue is that the tests in your repo pass while in the real world app, ProtocolEx is no longer accounting for some of the defimpl_ex implementations. And it's doing so virtually randomly.
At first, it didn't account for most (maybe even all) defimpl_ex in the web app of the umbrella project b/c the dependency and the compiler was only set in the domain app (that still used to work 100% ok on Elixir 1.14.5). So, I added those to the web app mix.exs as well. However, it only partially fixed the problem for some of the defimpl_ex in the web app are still not accounted for although despite the fact they all get compiled.
It's obvious this is due to some changes introduced in Elixir 1.15, but it's extremely hard for me to understand which exactly.
This regards the problem I first mentioned here yesterday: https://elixirforum.com/t/protocolex-extended-protocol-library-using-matchers/6822/10
I use ProtocolEx extensively, so it's all over my (umbrella) project, both in the domain and the web apps. The issue is that the tests in your repo pass while in the real world app, ProtocolEx is no longer accounting for some of the
defimpl_eximplementations. And it's doing so virtually randomly.At first, it didn't account for most (maybe even all)
defimpl_exin the web app of the umbrella project b/c the dependency and the compiler was only set in the domain app (that still used to work 100% ok on Elixir 1.14.5). So, I added those to the web appmix.exsas well. However, it only partially fixed the problem for some of thedefimpl_exin the web app are still not accounted for although despite the fact they all get compiled.It's obvious this is due to some changes introduced in Elixir 1.15, but it's extremely hard for me to understand which exactly.