Whoa! Community!

Over the past couple of weeks I've been looking into WO's .api format, thinking on how it might be extended to make it more useful and informative. The format can be made far more valuable, for both developers and tooling, by adding both human-readable documentation and a more detailed structural contract — what types bindings accept, how attributes outside the declared API are handled (if at all) and so on. A richer more informative API makes the elements both easier to use, and increases the ability of tools to validate and verify templates statically, catching whole classes of binding errors that can currently go unnoticed.

Of course, like everything I do in WO, this all eventually leads to ng-objects, since this work doubles as the creation of ng's eventual canonical element API.

The format's design is happening in in a designated github repository; htttps://www.github.com/undur/apiext-format. The format's current development version is based on and backwards-compatible with WO's original .api format. But if that compatibility turns out to hinder the design, we might change the design direction.

I encourage anyone with thoughts or ideas to pipe up and let me know, either directly or by filing an issue on the github repo.

• The .apiext github repository
• The AjaxSlim element reference generated entirely from element .apiext files.
• Element reference view generated from .apiext in Eclipse (video, 43sec)
• Use of .apiext documentation on element-hover in Eclipse (video, 2min)