ElixirWeekly

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

Here's what the latest issue looks like:

Issue #337

This week in Elixir

Build Dynamic Forms with JSON Schemas
Learn how to build forms without writing a single line of HTML by using JSON Schemas from this post by Peter. Just define your form as JSON file and it’s live!

Validating Phoenix Params with Ecto
Andrei shows us how to implement an easy way for validating request params in Phoenix with an Ecto Schema. No extra tools needed!

Announcing Vulnerability Scanning and Management for Elixir
Paraxial.io can now scan your Elixir project for vulnerabilities, and records a detailed audit trail for your regulatory and compliance needs.

Debugging and Tracing in Erlang
In the second and final part of this two-part series, Marcos dives into Erlang tools you can use for debugging.

Even more from around the Elixir community

Thinking Elixir: Winning the ML Prise Podcast

BeamRadio: Doing Well and Doing Good: Elixir Apprenticeships Podcast

Phoenix 1.7 Tutorial (liveview) Video

My Personal Tech Limbo (and Elixir vs Rust) Blog post

Dependency Inversion on Elixir Using Ports and Adapters Design Pattern Blog post

Adding a Table of Contents to Nimble Publisher Blog post

Image Processing in Elixir Blog post

Dockerize Phoenix + Tailwind Application Blog post

Naming Elixir Phoenix Context Functions Blog post

Building an Embeddable Web App with LiveState, Elixir, and Lit Blog post

TON Blog post

Fuelen/owl: A Toolkit for Writing Command-line User Interfaces. 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