phoenix-code-review

To review Phoenix code for best practices, analyze controllers, contexts, routing, and plugs to identify anti-patterns. This ensures correct separation of concerns, proper Ecto changeset usage, and secure routing before merging features.

Common anti-patterns in Phoenix controllers and contexts involve improper business logic placement and incorrect Ecto integration. Analyzing the code ensures business logic is correctly separated and changesets are used properly for maintainability.

You can check Phoenix routing and plug composition by analyzing the code for route verification and secure pipeline construction. This process identifies routing issues and validates plug composition to maintain framework architecture.

Yes, reviewing Phoenix contexts works directly with Ecto changesets by checking for proper integration and data validation. The analysis enforces correct separation of concerns within the context modules to ensure data integrity.

The best way to enforce separation of concerns in Phoenix Framework code is by analyzing controllers and contexts to ensure business logic is not improperly placed in controllers. This architectural review maintains code quality and framework adherence.