When writing a library to extend some functionality on top of Ecto, is it considered bad practise to namespace module using Ecto? For example Ecto.AwesomeModule. Or is this pretty legit?
Bad practice. Consider EctoAwesomeModule instead.
1 Like
The Hex Publishing guidelines discourage this; you should not use the namespaces of other projects:
If you are providing functionality on top of an existing package, consider using that package name as a prefix. For example, if you want to add authentication to Plug, consider calling your package plug_auth (or plug_somename) instead of auth (or somename).
Avoid namespace conflicts with existing packages. Plug owns the Plug namespace, if you have an authentication package for Plug use the namespace PlugAuth instead of Plug.Auth.
1 Like
