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
{{ message }}
This repository has been archived by the owner on Sep 23, 2022. It is now read-only.
FlareTail.js only has a simple fill method that renders Microdata (usually Schema.org). It would be nice to have support of if-else switches or for loops, so we can hide something (see bzdeck/bzdeck#281) or iterate over items.
Also, the view should be automatically updated once the data has been changed. We need Object.observe because Object.watch and Proxy are bad for performance, but no one is working on the new method...
<sectiondata-if="cf_user_story"><h4>User Story</h4><divitemprop="cf_user_story"></div></section><!-- this should be right after an element having the `data-if` or `data-else-if` attribute --><sectiondata-else>
No user story??
</section><!-- this should also work --><sectiondata-if-not="cf_user_story">
No user story??
</section>
<uldata-for="mentor"><liitemprop="mentor" itemscopeitemtype="http://schema.org/Person"><spanitemprop="name"></span><spanitemprop="email"></span></li></ul><!-- or use a template --><uldata-for="mentor" data-template="bug-mentor"></ul>
The text was updated successfully, but these errors were encountered:
It might be better to use comments instead of data-* attributes. NodeIterator allows us to iterate over comments like this, so <!-- if cf_user_story --><!-- else --><!-- endif --> can be found easily and the markup won't get messed up.
FlareTail.js only has a simple
fill
method that renders Microdata (usually Schema.org). It would be nice to have support ofif-else
switches orfor
loops, so we can hide something (see bzdeck/bzdeck#281) or iterate over items.Should we use template strings?
Also, the view should be automatically updated once the data has been changed. We need
Object.observe
becauseObject.watch
andProxy
are bad for performance, but no one is working on the new method...The text was updated successfully, but these errors were encountered: