ElixirWeekly

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

Here's what the latest issue looks like:

Issue #358

This week in Elixir

Absinthe for Large Elixir Applications
Discover how you can best use Absinthe for data-heavy Elixir applications in this article by Saban.

Unit Testing SQL Functions in an Elixir Project
If you ever needed to add an SQL function that you can use in your Elixir project you might have skipped writing tests for it. Andrei shows a way to test your SQL functions in your Elixir test suite.

Supercharge Your Elixir with Native Implemented Functions (NIFs)
Elixir/Erlang NIFs open up a world of possibilities to Elixir developers, but they're not as well understood as they should be.

Migrating from pow to phx.gen.auth
François posted this write-up on how to migrate from the pow library for authentication to phx.gen.auth without breaking anything for his users.

Even more from around the Elixir community

Elixir Outlaws: Elixir and Roses Podcast

Elixir Wizards: Chris McCord and Jason Stiebs on the Future of Phoenix Podcast

Thinking Elixir: Serving Up AI with Sean Moriarity Podcast

Sanitizing HTML with HtmlSanitizeEx Video

Elixir Emacs Development - 2023 Edition Blog post

Migrating to Verified Routes Blog post

Migrating Your Existing Ruby on Rails Codebase to Elixir/Phoenix Blog post

Testing Responsive Web Design with Phoenix On Your Phone Blog post

How ChatGPT Improved my Elixir Code. Some Hacks are Included. Blog post

Uploading Images In Phoenix Live View Blog post

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