Timo Tijhof 4854d644ee doc: Get rid of 'static' property container in jsduck index ... Us grouping the inheritable static properties that way is an implementation detail that is polluting the index and makes it harder to refer to individual identifiers. It also causes problems under JSDuck 5 because that version is more strict about defining properties (Foo.static.bar) of which the parent is not defined in the index (Foo.static), we'd have to add a sea of `@static @property {Object} this.static` all over the place. Might as well hide this implementation detail and just consider them static properties (just like we already do for "private" properties). Change-Id: Ibf2ebf7752aabc2b75b6ac6fa00e2284a181a600		2013-11-19 10:21:39 +00:00
..
annotations	Get rid of dmRendering hack in ve.ce.MWInternalLinkAnnotation	2013-10-28 15:49:08 +00:00
metaitems	Send the old category and language types to Parsoid for back compat	2013-11-04 19:41:19 -08:00
models	Make generic localization utility for lang code keyed objects	2013-11-13 14:26:51 -08:00
nodes	doc: Get rid of 'static' property container in jsduck index	2013-11-19 10:21:39 +00:00