We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To extend the concept introduced in #103 we could add a <yield> tag similar to that in Riot or Ember:
<yield>
<yield to="name">...</yield>
this.props.name
<yield from="name"/>
<yield />
this.props.children
<yield render="{this.someFunc()}"/>
this.someFunc()
Some examples:
<my-splitter> <yield to="leftpanel"><div>hello</div></yield> <yield to="rightpanel"><div>hola</div></yield> </my-splitter>
my-splitter.rt:
<tree> <yield from="leftpanel"/> </tree> <panel> <yield from="rightpanel"/> </panel>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
To extend the concept introduced in #103 we could add a
<yield>
tag similar to that in Riot or Ember:<yield to="name">...</yield>
would pass the element tree inthis.props.name
<yield from="name"/>
would render the tree passed inthis.props.name
<yield />
with no attributes would be simply a shortcut forthis.props.children
<yield render="{this.someFunc()}"/>
would render the tree returned fromthis.someFunc()
Some examples:
my-splitter.rt:
The text was updated successfully, but these errors were encountered: