Thanks @msaraiva for the detailed answer. In line with some of my thoughts. Once libraries like GitHub - surface-ui/surface_bootstrap · GitHub and GitHub - surface-ui/surface_tailwind · GitHub mature - probably both developer experience and productivity will reach the top of the ladder. Exciting times to be a Web Application Developer.
cvkmohan
cschmatzler
Might be a long shot, but did anyone manage to convert the VSCode syntax highlighting definition Marlus created to something that Sublime Text can read? Been trying a few automatic converters and they all fail.
msaraiva
Broadway Core Team
@cschmatzler feel free to open an issue at Issues · msaraiva/vscode-surface · GitHub and provide more information about the errors you get when running those converters. Maybe it’s something we can fix at the grammar level.
zimt28
After using Surface for a little bit I’m still wondering why the syntax
prop name, :string
was chosen over
prop :name, :string
It feels quite “unnatural”, is there a technical reason?
harmon25
When passing prop name to a component or dom node it is name="value" not :name="value" since props are =~ html attributes, it makes sense imo.
and attributes/props like :if have special meaning in the context of surface.
zimt28
Possible, I just think that it looks very unfamiliar 
Another question, I’ve built a table component as described here and it’s working well, but I cannot find a way to combine this with dynamic columns:
<Table data={resource <- @resources}>
{#for col <- table_columns()}
<Column label={col.label}>
{Map.get(resource, col.attribute)}
</Column>
{/for}
</Table>
It’s telling me that
a) The default slot wasn’t defined, when I define one it tells me that
b) resource is undefined
I’m not sure what I’m missing here 
msaraiva
Broadway Core Team
Hi @zimt28!
Defining props in Surface is as common as defining functions. You already define functions as:
def name, do: ...
So it shouldn’t be so unfamiliar 
Unfortunately, you can’t assign slots dynamically. The problem is that LV doesn’t have support for slots yet so in order to make it work, we need to know upfront how many blocks are being passed at compile-time to generate the proper case clauses in the component’s body. This is a limitation that can only be solved when Phoenix adds built-in support for slots, which is already on the roadmap.
msaraiva
Broadway Core Team
No. We’ll release a new v0.6 after Phoenix v1.6 is released. In the meantime, if you want to try Surface with LV 0.16, you need to use the Surface version on master.
im3000
Hey Surface users! Is there a way to validate only the current field in the form? The one that user interacts with. In LiveView you can achieve it by adding the data attribute. Does anyone know how to do it in Surface?
def error_tag(form, field) do
Enum.map(Keyword.get_values(form.errors, field), fn error ->
content_tag(:span, translate_error(error),
class: "form-error",
phx_feedback_for: input_name(form, field),
data: [phx_error_for: input_id(form, field)]
)
end)
end