elixir-antipatterns

Fix Ecto N+1 query issues by applying Repo.preload to optimize database queries and separating business logic out of Phoenix LiveView components into dedicated contexts.

The best way to handle business errors in Elixir is to return tagged tuples like {:ok, value} or {:error, reason} instead of raising exceptions, which ensures more robust and maintainable code.

Structure a Phoenix code review by checking for Elixir anti-patterns such as business logic inside LiveViews, missing Ecto query preloads, and ineffective ExUnit test assertions.

Yes, this Elixir code review guidance covers Ecto query performance by highlighting query optimizations like preloading associations and advising on appropriate database indexing to prevent bottlenecks.

You should move business logic out of Phoenix LiveView whenever it handles core domain operations, ensuring proper context separation to maintain clean architecture and improve Elixir code maintainability.

Write effective ExUnit tests for Phoenix contexts by focusing on clear assertion-based testing practices that validate the isolated business logic without relying on LiveView component rendering.