(Possible unrelated to the current discussion) For what it's worth, Typescript is pushing the metadata (decorators) concept forward [1] Angular2 is fully utilizing this concept in the form of annotations [2]
There is also a proposal to add metadata/decorators in Javascript directly [3] Looks like the industry is slowly starting to full on embracing the concepts introduced by Flex 3/4. For example Angular 1 and 2 support dependency injection. In the Flex world, Parsley, Robotlegs etc. easily added support for DI by utilizing the custom metadata support and runtime describeType (or its FlexJS equivalent) If we don't support custom metadata, it will make it very hard for 3rd party developers to add these kind of cool features. [1] https://www.typescriptlang.org/docs/handbook/decorators.html [2] http://www.angulartypescript.com/angular-2-annotations/ [3] https://github.com/wycats/javascript-decorators On Tue, Dec 13, 2016 at 8:19 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 12/13/16, 12:48 AM, "Harbs" <harbs.li...@gmail.com> wrote: > > >What I’d really like to do would be to define a class like this: > > > >package > >{ > > import stream.Stream; > > > > [Extern] > > public class JSZip > > { > > public function generateNodeStream(nsp: > NodeStreamParam):Stream{ > > return null; > > } > > } > > > >} > >And the compiler would know to generate externs from this class and it > >should “just work”. > > > >This would make it MUCH easier to create swc libraries of externs as well. > > File a JIRA. Although I would much rather use @externs instead [Externs] > > -Alex > >
