That’S not a problem of templating engines though. It’s simply how html/css interacts with whitespaces.
LostKobrakai
_rubenfa
The way forms are defined is pretty similar in Razor and EEX. You need a lambda or a function, maybe some CSS classes etc. But you only need a @ in Razor. For me, it’s a big deal. Also when you are adding strings from the model. In EEX it’s a little verbose.
This some times depends on the team. I have worked with people in charge of build things only with HTML and CSS. They didn’t know anything about C#, lambdas or models. With a lot of brackets, lambdas and other non-HTML things they had some problems. But it’s true that you have to know a lot of special directives and it could be hard.
Anyway, I agree with you. It is only a matter of taste, and I know that my request could be weird for Ruby developers.
0
wanton7
Yes but React has fixed it in template level and I can’t see why other template engines couldn’t do the same.
0
LostKobrakai
I’m not sure if that’s something “fixable”. As soon as you want to have <pre> tags to e.g. render code examples you need whitespace. Also if you’d use phoenix_html helper functions instead of eex templating you’d probably get to something quite similar to jsx (without whitespace).
0
wanton7
By removing only white space that is between HTML elements like React does. Text inside <pre> isn’t effected or white space inside foo bar in this <span>foo bar</span>. React JSX templates are proof that it’s “fixable” and works really well.
Edit: Here is how JSX does it How Whitespace Works in JSX
0
wanton7
JSX does remove new lines and leading and trailing white space. That might be problem if you want new lines in your text. React way is to put literal JavaScript string inside template when you need to preserve white space and new lines. So template needs to have support to preserve white space when need arises.
0
OvermindDL1
Just as a suggestion, if you could try to refrain from posting pictures of text it would be awesome, I’m often in a gui-less terminal and having to bring up the post on my phone just to realize the picture was text that could have been included in the post itself wastes a lot of time, plus you can’t highlight it, search for it, etc… ^.^;
EEX isn’t an html template language, it’s a text template language, and removing text that was explicitly put in the file would be very very bad for a variety of formats, even in HTML whitespace is very important, not just in <pre> tags but in a variety of other areas depending on CSS and javascript and all. Just casually wiping whitespace is pretty bad.
If you are wanting something more HTML-specific for templating then there are alternative template engines (and you can mix and match all you want too), like you might like:
Which looks like:
doctype html
html
head
meta name="keywords" description="Slime"
title = site_title
javascript:
alert('Slime supports embedded javascript!');
body
#id.class
ul
= Enum.map [1, 2], fn x ->
li = x
It keeps proper HTML, it uses selector tags to define elements, it uses = to delinate Elixir calls, etc… etc… It’s always looked interesting to me, but I’m too used to looking at html itself. ^.^
There is also django-like template and pug-like templates and more for elixir/phoenix as well, and it’s not hard to create your own either.
As for @ as a trigger key, that seems to only work for single line expressions, giving no control over how to handle output wrapping afterwards or how to handle multi-expressions or bindings or so? I prefer beginning and end delimiters, though I could see @(...) being useful.
3
_rubenfa
You are right. I thought it was a good example, but I don’t know why ASP .NET Core team put it into an image.
In Razor you can use multiline expressions with brackets @{...}. If you are using conditionals, for example, you have to use something like this:
@if(somethingTrue) {
<p>Its true</p>
}
0