ElixirWeekly

Get your Elixir News in a weekly email!

Elixir is one of the most vibrant eco-systems in programming right now. There's so much happening and our community is growing faster and faster every day.

ElixirWeekly means: stuff you easily miss, shared on ElixirStatus and the web, handpicked articles and community news in one nice weekly email.

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

Here's what the latest issue looks like:

ElixirWeekly by @elixirstatus

Issue #430

This week in Elixir

Mix test.interactive
Randy's mix test.interactive allows you to re-run your tests every time something changes while interactively controlling the arguments passed to mix test.

Phoenix: Test Smarter, not Harder
Freddy wrote/presented this guide on using phoenix_test and playwright to ensure feature stability in the face of technical changes.

The Saga Pattern in Elixir
Peter explores the Saga pattern in Elixir for managing complex, multi-step processes, showing choreography and orchestration approaches with code examples.

Create Your First LiveView Native App - Part 2
Let's build a LiveView Native App! Learn about forms, template references, and SwiftUI CoreComponents in Brian's post.

Even more from around the Elixir community

Elixir Friends: Andrew Ek Podcast

Thinking Elixir: A BeaconCMS of Hope Podcast

ParadeDB 0.11.0, Database Access Layers, AND YOU! Blog post

Bringing SOLID to Elixir Blog post

Elixir-error-tracker/error-tracker: 🐛 An Elixir-based Built-in Error Reporting and Tracking Solution Project update

tuncan v0.4.0 released Project update

Submit your blog post/project update

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