You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second example is using a belongs_to while the first one is using field :)
If you change it to belongs_to in the first example, you'll see that the compile-time dependency disappears :) In case Country was an Ecto.Type, then you would have to use field, but that compile-time dependency is actually introduced by Ecto, so there's not much we can do.
Guess I never responded to this 🫣
What you say makes a lot of sense, and we definitely can't remove a compile-dep that Ecto is adding.
Although what brings me here today is I found another case where typed_ecto_schema adds a compile-dep where Ecto doesn't have it, the join_through of a many_to_many:
Modules referenced as fields still create compile-time dependencies. e.g. this is an issue:
While this is not an issue:
I've created a simple phoenix project that serves as a reproduction of this issue: https://github.com/axelson/typed_struct_compile_repro
In it I expect this command to not show any compile-time dependencies, but instead it shows one compile-time dependency:
I believe this is a subset that was not fixed with #18 (original issue filed as #6)
The text was updated successfully, but these errors were encountered: