I’ve written a few non-LiveView Surface components and never had to reach out for <%= yet. It might take some time to get used to <. syntax for function components. Surface’s module-based <Thing> is something that I’ve seen a lot in React, so it’s more “natural” on the eyes.
stefanchrobot
0
cvkmohan
cvkmohan
Yes. That is some confusion. This is one area I felt Surface is more consistent with its syntax.
As of now, my feeling is - surface will always be HEEx@next using LiveView. Let us see how it goes.
0
focused
Maybe I missed something, but I don’t understand one thing. In this example why there are no inner components like input/select/submit? For example (pseudosyntax):
<div class="flex mt-6 mb-8">
<.form let={f}
for={@changeset}
phx_submit="move_items"
phx_target={@myself}>
<div>
<.select for={f, :category_id, @category_select} prompt="Move to list"/>
<.submit value="Move"/>
</div>
</.form>
</div>
It would be more readable. Will those helper components be included in future releases of phoenix?
0
LostKobrakai
I’d be curious about that as well. I recently talked to someone on slack who put a huge list into a select and wondered, why the options on select inputs weren’t granularly diff’ed.
0
chrismccord
Creator of Phoenix
The driving factor around {} for elixir within an HTML tag is eex is awkward when trying to handle attributes inside a tag, for example:
<div id="<%= @id %>" class="<%= @class %>">
vs
<div id={@id} class={@class}>
It’s a tradeoff for learning, but this is exactly why we kept regular <%= %> EEx rules outside of HTML tags. I hope that give some insight. The syntax is a 1000% upgrade for me 
12
cvkmohan
Agree. It is just that - as a developer - now I have to put up some elixir code in this template. Should I be using <%= %> or {} is a question that needs to be answered every time. Probably with some practice we do get there. But, that is what I understood out of @thousandsofthem comment.
0
chrismccord
Creator of Phoenix
sodapopcan
I personally have no problem remembering this but just out of curiosity (and maybe this is in a gh discussion somewhere which I’d be happy to read) why not {} everywhere?
0
chrismccord
Creator of Phoenix
It would be a severe deviation from eex and I’m not a huge fan of it for larger code blocks
3