Makes sense—just wondering. Thanks!
sodapopcan
LostKobrakai
Such a change would also affect all the control structures and do/…/end blocks of e.g. macros. EEx also has <%=, <%#, <%% and few yet to be used tags, which at some point people would ask for. Most of those are unlikely to be used for html attributes though 
0
karolsluszniak
For me personally, Heex’s mixed interpolation syntax was an easy and natural switch. And a huge relief actually since writing Eex attributes was always cumbersome and er-prone for my fingers.
If only there was Heex syntax highlighting for Sublime… (or am I the only one who doesn’t use vscode..? ;))
Update: thankfully not https://github.com/princemaple/elixir-sublime-syntax/issues/28
0
sodapopcan
I’d actually thought of the extra EEx tags after I asked the question but figured I’d just leave my question as it was. I’m actually quite happy with this decision as I like EEx tags but see the {} in attributes as a big win. I was just wondering what made the Phoenix team not take this “all the way”. It shows some good restraint!
0
chrismccord
Creator of Phoenix
yeah TBD on more components. We simply didn’t have enough time to arrive there but definitely on our list 
3
gabriel137
Sebb
So I just gave this a try.
--live does not generate a LiveView anymore, so I was forced to RTFM 
.
So for all other lazy newbies, here’s what’s to be done to get a minimal liveview running:
mix phx.new hello --live --no-ecto
add lib/hello_web/live/hello_live.ex
defmodule HelloWeb.HelloLive do
use Phoenix.LiveView
def mount(_, _, socket) do
{:ok, assign(socket, :attrs, %{})}
end
def handle_event("hide", _, socket) do
{:noreply, assign(socket, :attrs, %{"style" => "display: none"})}
end
def handle_event("show", _, socket) do
{:noreply, assign(socket, :attrs, %{})}
end
def render(assigns) do
~H"""
<div>
<button phx-click="hide">hide</button>
<button phx-click="show">show</button>
<div {@attrs}>Welcome to Phoenix!</div>
</div>
"""
end
end
change this in lib/hello_web/router.ex
scope "/", HelloWeb do
pipe_through :browser
- get "/", PageController, :index
+ live("/", HelloLive)
end
mix phx.server
Important: do not just count the lines output by this call and think its stuck for half minute… 
It just takes no time to startup. 
2
josevalim
Creator of Elixir
For completeness, you can totally use npm with esbuild. If you call “npm install topbar” inside the assets directory after phx.new and then import topbar, it will 100% work.
You only need to migrate esbuild itself to npm if you need plugins, which we detail here: Asset Management — Phoenix v1.6.0-rc.0
3
cvkmohan
This is why I felt the decision to remove node from the base setup has been a great leadership decision. Once, node is in - why just esbuild via npm? why not webpack? why not snowpack? why not vitejs ? The options will be too many with no clear winner.
If going via the npm route - I would think instead of esbuild, better to go with vitejs, as vitejs uses esbuild under the hood and we get even postcss support right away. Just for the record A proof-of-concept integration of Vite.js (modern JS/assets bundler) with Phoenix + Liveview - #2 by 50kudos this post worked well for replacing webpack with postcss. The performance in development looked similar to what we are getting via esbuild.
0
romaluca
After that i upgraded Phoenix 1.6 and LiveView 0.16.1 i have this issue:
in a LiveView template heex there is this code:
...
<%= for i <- @topics do
render "topic.html", topic: i
end %>
...
if i launch my webapp i receive this error:
** (ArgumentError) lists in Phoenix.HTML and templates may only contain integers representing bytes, binaries or other lists, got invalid entry: %Phoenix.LiveView.Rendered{dynamic: function<4.81847032/1 in SWeb.CommentView.“topic.html”/1>, fingerprint: 98279643322116372238403084114730099928, root: false, static: [“\n”, “”]}
I tried also with render_many but is the same.
How can i do?
0