manhvu
In a large repo, working with module need to add alias too much is quite annoyed and not good for organizing code.
I think better add support for namespace can bring more convenient for dev.
This is a basic example for namespace cross multi modules.
Example:
defmodule MyApp.A do
namespace MyApp.DataProcessing
def a do
# do somethings
end
defmacro macroA(name, opts) do
#...
end
end
defmodule MyApp.B do
namespace MyApp.DataProcessing
def b do
# somethings
end
end
defmodule MyApp.C do
namespace MyApp.DataProcessing
def do_something(data) do
data
|> A.a()
|> B.b()
end
A.macroA :wrapper, type: :json
end
LS can easily to suggest dev in a namespace.
Pros:
- Less typo like add alias for module.
- Make code clean than before.
- Better for LS suggest in case work in namespace.
Cons:
- Make complicated if bring support for
import,requireoruse. - Can make dev confused.
Trending in Proposals: Ideas
I recently learned about this API and was surprised there’s no explicit support for it in the the Phoenix.
Example use cases:
A webs...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex











Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
This idea is essentially implemented in the library Boundary GitHub - sasa1977/boundary: Manage and restrain cross-module dependencies in Elixir projects · GitHub
Do you have any thoughts on how this proposal differs, beyond basically the implicit aliasing?
FlyingNoodle
Please don’t. I know this isn’t a democracy but I vote against it.
BartOtten
At mobile so in short:
Now you can
use DataProcessingAliasesin the modules. Mixed ground between explicit and implicit…?Last Post!
BartOtten
Ah, forgot about that. Need to expand it before passing it as function argument. Small change but then you can just use module names.