kelu
I’ve started a question on SO about my problem so I won’t go into much details here. In general I have trouble with the same module getting defined twice in dependent projects.
Please check it out:
http://stackoverflow.com/questions/38213089/duplicate-protocol-implementations-in-dependent-projects
For me it seems like a bigger issue with dependencies. Is there some way I could solve this from my code side (like not modifying dependencies)?
Also I am able to modify one of them (not Ecto obviously) but what would be the best practice here? To avoid having the same module defined twice
Regards
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kelu
Hey guys, I’ve started bounty on this question as I think it really should get more love and deserves some ideas how to solve the problem with implementing Protocols for the same other types in different projects. Please give it some thoughts!
Last Post!
kelu
I think the most reasonable would be to convince guys from Ecto to put the implementation of this protocol into another simple dependency (all in all this implementation is modifying two outside dependencies - Decimal and Poison, it doesn’t have anything to do with Ecto at all). This way also Gold should dependend on this new dependency and everything would work, but I guess it wouldn’t be easy to convince guys from Ecto to do that… Maybe later I’ll open this as a suggestion at their google groups