We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Inspired by a conversation on Bsky (Thanks Netto) about the release of Phoenix LiveView 1.0.
The release of Phoenix LiveView 1.0 was announced yesterday! Hooorayyy! 🎉🥳
With numerous improvements aimed at simplifying the framework's usage. One of the major enhancements stands out: the move from
<%= %>
to{}
for rendering templates.And I missed one more enhancements in terms of ergonomics when is calling components. Calling functional components in Phoenix LiveView is straightforward and seamless, making the developer experience intuitive. However, when dealing with live components, the syntax and approach differ significantly. This inconsistency can disrupt the ergonomics of the framework, especially for newcomers or teams striving for code simplicity and uniformity.
Here's an example to ensure we're on the same page and to illustrate the topic I'd like to explore further in this blog post.
continue reading on dev.to
⚠️ This post links to an external website. ⚠️
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.