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
I just realised there's redundant information about what is style attribute and html/imba attribute.
We write:
<div[h:20remw:10rem]attribute=some_data>
But we could write:
<divh:20remw:10remattribute=some_data>
# or
<divattribute=some_datah:20remw:10rem>
# or even
<divh:20remattribute=some_dataw:10rem>
As parser can recognise what is for style and what is another by : and = characters.
I would propose an alias for tag imba-component and allow simply:
<imba-component>
# as an equivalent of
tag imba-component
<self>
Parser can understand it's a tag declaration because there's no indentation. It could lead to super clean - especially small - files which look just like html.
Both upper proposals are backwards compatible and following not. I'd like to remind one feature of Imba1 which was very clean passing data to the component, like this:
<some-component[person]>
# and then object was accessed inside some-component through `data` like this:
data.name
I was using it a lot and it is great for decorating object - which for example came straight from backend - with a visual part.
Considering that you like 1) proposal it would be possible to reintroduce that feature.
I would change data into some symbol, for example @ so we could write something like this:
tag person-component
<self>
<div> @name
<div> @surname
# and use it
<person-component[person]>
Pick any or none as you like.
The text was updated successfully, but these errors were encountered:
We write:
But we could write:
As parser can recognise what is for style and what is another by
:
and=
characters.tag imba-component
and allow simply:Parser can understand it's a tag declaration because there's no indentation. It could lead to super clean - especially small - files which look just like html.
I was using it a lot and it is great for decorating object - which for example came straight from backend - with a visual part.
Considering that you like 1) proposal it would be possible to reintroduce that feature.
I would change
data
into some symbol, for example@
so we could write something like this:Pick any or none as you like.
The text was updated successfully, but these errors were encountered: