ElixirWeekly

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

Here's what the latest issue looks like:

Issue #324

This week in Elixir

Plucking the "A" from PETAL
This post asks if we can remove Alpine from the PETAL stack. Can we do everything we need with just LiveView?

Doing Things Only Once in Elixir
Danie writes about a simple solution to the stampeding herd problem and a library that wraps it up.

Phoenix LiveView v0.18: New Special HTML Attributes
The folks at AppSignal check out Phoenix LiveView 0.18’s new special HTML attributes to help you write cleaner HTML.

Prevent Overlapping Time Ranges with Ecto and Postgres
Exclusion constraints in Postgres can efficiently detect overlapping bookings, appointments, and schedules and block their creation. Peter explains how to implement them using Ecto.

Even more from around the Elixir community

Thinking Elixir: Localize and Personalize Your Elixir Apps Podcast

Elixir & Phoenix Fundamentals Full Course For Beginners Video

Chatbots as User Interface with Elixir - ElixirConf Africa 2022 Video

LiveView Native Weekly #5 Blog post

Expose GraphQL Operation in Logs with Absinthe Blog post

State Machine in Elixir Using Erlang’s gen_statem Behaviour Blog post

Detecting SQL Injection in Phoenix with Sobelow Blog post

Adding Elixir to Erlang via Rebar3 Blog post

Probuild Ex Part Three Blog post

Elixir vs Cybersecurity - is Elixir Language a Safe Technology? Blog post

KronicDeth/intellij-elixir 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).

ElixirWeekly by @elixirstatus

ElixirWeekly

Questions & Answers

Contact