travisf
I picked this pattern up from another dev and have made fairly extensive use of it with Multis:
@multi Multi.new()
...
@multi
|> Multi.put(:params, params)
|> Multi.run(:somefunc, &some_func/2
This ensures that pipechains start with a raw value and, I think, it looks a little cleaner. Does anybdy else do this? Are there any articles on this pattern? It’s fairly simple but there is some nuance due to the constraints of module attributes (I’ve only done it with Ecto.Multi.new/2 and raw values), I wonder if you would run into problems during compile time if you tried it with modules in your project. Of course you couldn’t do it with a function in the same module.
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
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
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
andyleclair
How does it ensure the pipe chain starts with a raw value?
IMO I would not do this. We have some legacy tests that use module attrs and they are a bit of a PITA to deal with and refactor.
If you want your pipe chains to start with a raw value, maybe use credo?
sodapopcan
Not to pile on but I’m really not a fan of things like this. This is really no different than a single-line private function that I have to jump to to be sure of what it is. It’s also creating a compile-time dependency on
Ecto.Multiwhich isn’t a huge deal in this case but not ideal. I agree with @andyleclair that credo is the best tool for the particular outcome you’re looking for.dimitarvp
This is a complete no-go, module attributes basically get replaced with their value at compile time which also means that you might get 2 different
Multi.newvalues (though I have not tested this so it’s likely not true).But as the others said there’s zero value in this.
Multi.newis not an expensive operation either so your reason to try to do this is quite puzzling. What’s your rationale? “Looks little cleaner” is, I am sure we all agree, a very subjective statement, and even if we agree that it’s kinda sorta objective there are still degrees; you are gaining next to nothing by doing this replacement with a module attribute.andyleclair
I have seen this attitude before in people who are just learning elixir, fussing over micro things that map to things they know from other languages.
My advice is: don’t worry about it! Write the most straightforward, obvious code you can, and go back to make it faster later if you need to. Always heed the words of Saint Joe:
“Make it work, then make it beautiful, then if you really, really have to, make it fast. 90 percent of the time, if you make it beautiful, it will already be fast. So really, just make it beautiful!”
acangiano
I tend to use module attributes as storage for compile-time constants, which is particularly handy for “caching” expensive operations with no runtime dependencies. I don’t think that what you’re doing is particularly bad but it feels unnecessary.
travisf
From the responses; I will stop doing it. The one thing I’m a little confused about is when you say “If you want your pipe chains to start with a raw value, maybe use credo?” I’m not sure exactly what you mean?
I actually got into this habit because of credo, although I can see that it’s now off by default but I think at one time the codebase I was throwing PiepChainStart warnings.
al2o3cr
I’d be surprised if starting a chain with
Multi.new()triggers that Credo check - there is specific code to allow that shape when there are no args:https://github.com/rrrene/credo/blob/v1.7.5/lib/credo/check/refactor/pipe_chain_start.ex#L205-L211
dimitarvp
As a guy working with Elixir for 8 years now, I am confused as well.
sodapopcan
I was confused by “make sure it starts with a raw value” and how this pattern would solve it. I probably should have just asked but instead I ass-u-me’d you meant to ensure you use
Ecto.Multi.new()over%Ecto.Multi{}. Credo in this case could just make sure that the latter isn’t used anywhere other than on the left hand side of a pattern match (or guard, I suppose).andyleclair
Sorry, what I meant was “use a credo rule to enforce this”