liveview-code-review

To review Phoenix LiveView code for best practices, analyze .heex templates and LiveComponent modules for lifecycle patterns, optimal assigns and streams usage, component implementation, and security vulnerabilities like unvalidated inputs and sensitive data exposure.

The best way to manage data in Phoenix LiveView is using streams for large, paginated lists to avoid socket copying issues, while using assigns for standard data management to ensure optimal performance and maintainability.

To check if your LiveView lifecycle patterns are correct, review your implementation of mount, handle_params, handle_event, and handle_async to ensure they follow established Phoenix best practices for efficient real-time development.

Yes, you can audit Elixir LiveComponent modules for sensitive data exposure by analyzing the code to identify potential security risks, including unvalidated inputs and accidental inclusion of sensitive user data in assigns.

Your Phoenix LiveView dashboard may have performance issues with large lists because of socket copying from excessive assigns, and switching to streams for paginated data management can resolve these bottlenecks.