On 3/10/23 3:33 PM, Austin Ziegler wrote:
1. The warning that I think is being discussed is a compile warning
for the library *dependency*, not for the hosting application,
which matches what I have seen.
This.
I'm working on creating a focused way of reproducing it, but need some
time to get it all dialed in.
Essentially though, you are right.
What we are working on is a way to put Ecto models into a library
dependency that can be brought into other applications. But for this to
work, we have to abstract the definition of Ecto.Repo and defer it to
runtime. However, because dependencies are pre-compiled, you then get
these warnings.
This is a use case that's very compelling, and yet it goes against how
things work right now with the way dependencies are, but that doesn't
remove the value of having something like this.
oban is a great example.
-Brandon
--
You received this message because you are subscribed to the Google Groups
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elixir-lang-core/194c5d9c-6ba3-6599-0436-caae01bec86c%40cold.org.
