elixir-antipatterns

To fix Elixir anti-patterns like N+1 database queries, review your Phoenix application code to identify inefficient data fetching and apply correct query implementations. Refactoring these problematic patterns optimizes database interactions and improves application performance.

The best way to handle business errors in Phoenix is to avoid using `raise` for expected business logic failures. Instead, return explicit error tuples and pattern match them in your LiveView, ensuring proper separation of concerns between view rendering and business logic.

Business logic should be moved out of Phoenix LiveView components to ensure proper separation of concerns. Placing application logic directly in views creates maintainability problems and anti-patterns; refactoring it into dedicated context modules makes the Elixir code more robust and testable.

To review Elixir code for Phoenix anti-patterns, systematically check for common pitfalls like using `raise` for business errors, N+1 database queries, and misplaced logic in LiveViews. Compare problematic implementations against correct refactoring examples to ensure robust application architecture and proper error handling.

Yes, this Skill can detect architecture anti-patterns in Elixir applications. It identifies critical architectural issues across error handling, database queries, and testing, providing clear examples of incorrect versus correct implementations to facilitate effective code review and refactoring.