How one developer added a rich-text editor without migrating existing plain-text data

A developer faced the challenge of upgrading an email body column to support rich-text formatting while preserving hundreds of existing plain-text rows without any database migration. The solution relied on a runtime format-detection function that uses a targeted regex to determine at read time whether a stored value is HTML or plain text. Three separate rendering helpers were written to handle display, editor loading, and plain-text previews, ensuring legacy content rendered correctly across all contexts. A key complication arose with the Trix editor and Livewire, where server-side logic had to be mirrored in JavaScript to correctly format values pushed to an already-mounted editor after page load. The author acknowledged the duplication as a deliberate trade-off, cross-commenting both code paths to make any future divergence easier to detect and debug.