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

Here's what the latest issue looks like:

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

How to Report Postgres Custom Errors in Ecto Changeset
Jakub shows us how to capture a Postgres custom error in the Ecto.Changeset without raising an exception.

Livebook 0.13: Expose an HTTP API from Your Notebook
This post explains how to expose API endpoints directly from your Livebook notebooks with the new Kino.Proxy feature in Livebook v0.13.

Learning Elixir as a Frontend Developer
Oliwer's reflections on learning Elixir and Phoenix with a primarily frontend background.

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 :)


Feedback? Questions? Anything else?

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