This does actually strike a chord for me and I'm realizing this is likely a
related question or perhaps the same question in another form. Is there some
way to define a module that a dependency can use at compile time or at runtime
without these warnings? Like a module that you want compiled
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
1. This is from code that last ran on Elixir 1.10 (it is currently
offline with no plan to bring it back online).
2. The dependencies include Phoenix (1.5.4) and phoenix_html (2.14.2).
It’s referring not to MyApp.Repo, but to Phoenix.View.
3. Phoenix and phoenix_html were compiled
Can you please provide a small app that reproduces the issue?
Even if the module comes from a transitive dependency, Elixir should be
able to see it and avoid the warning.
On Fri, Mar 10, 2023 at 5:00 PM Brandon Gillespie wrote:
> I'm in the process of breaking our larger/monolithic app into
I'm in the process of breaking our larger/monolithic app into separate
repos so we can bring the pieces in as dependencies on other apps.
However, a key problem we are running into is ultimately around the
database models.
We're working on a separate thing around most of that, but at the
