ElixirWeekly

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #144
This week in Elixir

Params Modules for Phoenix
The Params modules pattern can be used in Phoenix to validate and massage a controller action’s params into data that can be passed to contexts.

Nightly Tasks with a GenServer
Eric set up a nightly process that uses OTP primitives to run nightly tasks for his games. Nice!

ExDoc v0.20
Wojtek wrote about keyboard shortcuts, autocompletion, full-text search, and other stuff in the latest version of ExDoc.

Micro: Read cmd line pipes in elixir
Regis wrote a blog post about reading pipes from the command line in Elixir CLI tools.

Cleaning up Phoenix Controller Actions
Damon writes about a pattern he came across that helps when you need to pass a lot of variables to the view / template.

Elixir protocols, how do they work? the erlang perspective
Mariano gives "the erlang perspective" on protocols in Elixir.

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)

Contact

Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).