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

Here's what the latest issue looks like:

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

Analyze Meta Tags With Elixir
A quick walk through on how to analyse for meta tags on websites using Elixir.

An Introduction to Mocking Tools for Elixir
Let’s explore three mocking tools you can use in Elixir — Mock, Mox, and Mimic.

Using our One and Done Library to Power Idempotent API Requests
Add idempotency to your Phoenix/Plug apps with as little as one line of code using the new One and Done hex package!

Ecto v3.10.0 released
Ecto v3.10 is out with some exciting improvements around changesets, some of them focused on better interplay with LiveView.

Even more from around the Elixir community

Elixir Wizards: Michael Lubas on the Future of Elixir Security Podcast

Thinking Elixir News Podcast

Ash Primer: Calculations Video

Inspecting LiveView Payloads with liveSocket.enableDebug() Video

Simulate LiveView Latency with liveSocket.enableLatencySim() Video

Elixir Security: What's the Impact of DoS due to Atom Creation? Blog post

Deploy Notebooks as Apps & Quality-of-life Upgrades - Launch Week 1 - Day 1 Blog post

Distributed² Machine Learning Notebooks with Elixir and Livebook - Launch Week 1 - Day 2 Blog post

Hubs and Secret Management - Launch Week 1 - Day 3 Blog post

Crafting Your own Static Site Generator Using Phoenix Blog post

Exploring Functions, Data Structures, and Strings in Elixir Blog post

Phoenix LiveView Zipped Uploads Blog post

Learning Elixir Blog post

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