You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is an idea for a feature, and it's in a really crude phase intended to trigger a discussion.
I use the ViewComponent library a lot - it is very useful, but I've found that rendering them is pretty cumbersome and it pollutes templates a lot. I also use JSX, and its approach gave me an idea: Slim could, in an opt-in fashion, also make use of the fact that HTML tags are usually lowercase, so uppercase tags offer a new, vacant namespace.
As is evident even from this small example, there would have to be a syntax addition for the block parameter. Other approaches are possible for this, including:
An ideal implementation wouldn't hardcode ViewComponent as an optional dependency, but would rather allow the user to define a handler (or override the default one) for uppercase tags, should they opt to switch on the feature.
The text was updated successfully, but these errors were encountered:
This issue is an idea for a feature, and it's in a really crude phase intended to trigger a discussion.
I use the ViewComponent library a lot - it is very useful, but I've found that rendering them is pretty cumbersome and it pollutes templates a lot. I also use JSX, and its approach gave me an idea: Slim could, in an opt-in fashion, also make use of the fact that HTML tags are usually lowercase, so uppercase tags offer a new, vacant namespace.
So what we write now like this:
could be written like this:
As is evident even from this small example, there would have to be a syntax addition for the block parameter. Other approaches are possible for this, including:
An ideal implementation wouldn't hardcode ViewComponent as an optional dependency, but would rather allow the user to define a handler (or override the default one) for uppercase tags, should they opt to switch on the feature.
The text was updated successfully, but these errors were encountered: