Include condensed type definition file of Closure library

[jgiles]

We should include a JSON type definition file for the contents of the Closure library, and optionally load that definition according to a configuration setting.

The file could be rather large - it's possible we would need to settle for a subset, or break up the library into chunks.

There could be some trickiness to encoding all the type information we are interested in, since some aspects of the Closure type system (inheritance, unions, etc) are not explicitly supported as part of Tern.

[angelozerr]

Just for your information, I'm developping several tern plugins,I use JSON type definition and I follow those rules :

1. JSON type definition must be generated (from Javascript source by using YUIDoc, JSDoc, JSDuck, etc according the JS framework).
2. the tern plugin is generated too to manage several version of the JSON type definition. I have a tern plugin per version.
3. the generation is done with Grunt task and grunt template.

See for example https://github.com/angelozerr/tern.jsduck

Perhaps you could do the same thing to provide a closure plugin per version.

[jgiles]

Hmm, I hadn't thought about generating defs/plugins for each version of Closure.

The Closure library is weird in that as far as I can tell there aren't explicit release versions - everyone just runs against HEAD all the time.

I will probably just include a current snapshot of the Closure library with each new release of tern-closure. Automating that through Grunt is a good idea though.