bubbletea-code-review

To check BubbleTea code for Elm architecture anti-patterns, review your Go source to ensure the model/update/view separation is maintained, tea.Cmd handles asynchronous operations, and no blocking I/O runs inside the Update function.

Your BubbleTea TUI freezes during Update operations because blocking I/O is running synchronously inside the Update function, violating Elm architecture conventions; asynchronous tasks must be dispatched as tea.Cmd commands to keep the event loop responsive.

The correct way to use tea.Cmd for asynchronous operations in BubbleTea is to return commands from the Update function for non-blocking execution, ensuring the model remains immutable and the view renders without waiting for I/O tasks to complete.

You can review Lipgloss styling conventions in your Go TUI code by validating that style definitions are composed correctly and consistently, ensuring your BubbleTea components follow standard Elm architecture patterns for rendering and state management.

To validate immutability in BubbleTea model states, review your Go code to ensure the Update function returns a new model instance rather than mutating the existing state, preventing common anti-patterns that break the Elm architecture data flow.

Common BubbleTea component composition mistakes to look for before merging include mutable model states, blocking I/O in Update functions, improper tea.Cmd usage for async operations, and deviations from standard Elm architecture model/update/view patterns.