Kobrakai

At work we had been using elixirkit for a small menu bar app some time last year.

The introduction of HEEx in Phoenix 1.7 and the shift toward rendering HTML with function components brought significant changes to how data is transformed into HTTP responses in Phoenix.

Phoenix, the powerful Elixir web framework, is renowned for its real-time capabilities.

One of my most liked posts on the elixir forum has long been a post, where I shed some light onto what quote/2 and unquote/1 are about in metaprogramming on elixir.

While phoenix used websocket connections for a long time for its Phoenix.Channel abstraction there wasn’t really a good way to use websocket directly up until phoenixs latest major release (1.7).

With Phoenix LiveView becoming more and more popular people try to build more dynamic forms than before.

With Elon Musk taking over Twitter many, especially tech savvy, people have been looking at Mastodon as an alternative – and so did I.

The introduction of HEEx and function components to Phoenix LiveView brought a lot of improvements for building and maintaining UIs in html to the Phoenix community.

When doing JSON APIs in phoenix one will eventually hit the fact that by default structs cannot be encoded to json by Jason, the default json library of phoenix.

A common occurance in my phoenix applications is the need to render a list of some items – say companies in a job board application.

The recent ecto 3.5 update introduced the parameterized type Ecto.Enum, which is a great way to use atoms in elixir for signifying things like statuses or types of data.

When using phoenix_live_view people are often worried about their LiveViews being mounted twice for fresh requests.

Child specs are often confusing for people trying to convert the old Supervisor.Spec based syntax to the newer child spec based syntax, people trying to integrate with erlang libraries or because they added more parameters to their start_link functions and

People starting out with ecto are often confused by all the methods of getting changes applied to a changeset and therefore the database.

On the Slack Channel for Elixir there’s often the situation of people coming from other languages/frameworks to elixir and especially ecto to ask about “How to model many-to-many relationships”.

I've thought that @rails deployment on a non-Docker or non-Heroku production server was tricky.

You probably know the default parameters of a phoenix controller action callback: def index(conn, _params), do: […] or def create(conn, %{"entity" => entity_params}), do: […].

Phoenix 1.3 introduced the concept of contexts in a application.

For a project of mine I recently needed to keep the history of state changes for an entity in my database.

Getting straightforward HTML templates rendered in Phoenix is really easy.

Bei der Thematik von Styleguides und Pattern-Bibliotheken sind sich heutzutage wohl die meisten Entwickler darin einig, dass sie ein wertvolles Tool sind, um ein Projekt auch von Seiten des Interfaces modular zu gestalten.