bahner
Renaming and splitting packages in hex
I have worked a lot on my myspace_ipfs package and I am ironing out the creases. But learning Elixir and making a package this big was not so smart.
The quality has become OK and I find it good enough to qualify for a smaller namespace name, eg. ex_ipfs.
But it is too big. (And the name is too long). There are just to many tests to be written, so I’ve lost some momentum. I use the core parts myself and find that I like them. So I thought to relaunch the core parts as
ex_ipfs
and then add sub packages like
ex_ipfs_pubsub
ex_ipfs_files
ex_ipfs_swarm
Or something to that effect. How does the community feel about renaming packages (and thus polluting the name space). And what is the general feeling about splitting packages up into smaller parts?
Most Liked
dimitarvp
Well, just try to search for opentelemetry on hex.pm and you’ll see that your example is very tame. ![]()
In short: that’s absolutely fine, as long as you don’t drown in complexity of project A depending on B depending on C depending on A etc. That’s one type of complexity that kills motivation (and time, and energy).
BartOtten
Sometimes it’s for the better. Especially as it allows other developers to onboard by starting a subpackage/extension.
Popular in Discussions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









