Bartosz Dziewoński 3f0f302577 Enforce that some files must not use the ve global ... Previously, the ve-mw/init/ directory contained two kinds of files: those that were used when initializing VE, and those that may be loaded even if VE is not going to be initialized at all. The latter kind must not use the `ve` global variable. After moving those files to ve-mw/preinit/ we can enforce this with .eslintrc.json in that directory. This would have prevented T228684. (Technically they merely must not use `ve.init`, and may use `ve`, but that's harder to enforce. We should instead move the few non-init methods out of `ve`: now, track, trackSubscribe, trackSubscribeAll). Also, group some files under ve-mw/init/: targets/ now (only) contains ve.init.mw.Target and its subclasses, apiresponsecache/ now contains ve.init.mw.ApiResponseCache and its subclasses. Bug: T228684 Change-Id: I945249a27f6a0fa10a432d5c5dc57bc7e0461fd8		2019-10-10 15:15:40 +00:00
..
ve.init.mw.ArticleTarget.js	Enforce that some files must not use the ve global	2019-10-10 15:15:40 +00:00
ve.init.mw.DesktopArticleTarget.js	ArticleTargetEvents: clean up some duplication	2019-09-30 11:29:01 -05:00
ve.init.mw.MobileArticleTarget.js	ve.init.mw.MobileArticleTarget: Really deactivate the surface	2019-09-09 20:00:53 +02:00
ve.init.mw.Target.js	Enforce that some files must not use the ve global	2019-10-10 15:15:40 +00:00