Continuation of LiveView Native's Journey Toward Version 0.2

108
clicks
Continuation of LiveView Native's Journey Toward Version 0.2
Brian Cardarella explores the ongoing development of LiveView Native (LVN) and discusses the challenges of aligning SwiftUI's conventions with Phoenix LiveView, which was initially web-only. Initial approaches involved adapting SwiftUI view names to fit within Phoenix's naming constraints, leading to less intuitive tag naming. Efforts to bypass these constraints led to discussions with Phoenix and Elixir maintainers resulting in key changes, like allowing multicharacter sigils, which enhanced ergonomics for LVN developers. The article touches on organizational conventions for naming and structuring Elixir projects, aiming for consistency and ease for the community. It further looks into architectural changes and the need for upstream modifications in Phoenix to support format-specific layouts in LiveView, which could enhance developer experience and code reuse. The LVN team is prepping for these changes in anticipation of their adoption upstream.

© HashMerge 2024