mediawiki-extensions-Visual.../.docs/mw-categories.json

[
	{
		"name": "VisualEditor (MediaWiki extension)",
		"groups": [
			{
				"name": "Initialization",
				"classes": [
					"ve.init.mw*",
					"ve.version"
				]
			},
			{
				"name": "User Interface",
				"classes": [
					"ve.ui.MW*Page"
				]
			}
		]
	},
	{
		"name": "Upstream (MediaWiki)",
		"groups": [
			{
				"name": "MediaWiki",
				"classes": [
					"mw.Title"
				]
			}
		]
	}
]
Use submodule for VisualEditor core * Add lib/ve. * Remove modules provided by VisualEditor core. * Update paths. * Remove VisualEditor core specific things from Gruntfile. * Remove entries from external.js already in lib/ve/.docs/external.js. * Implement build script to compose a jsduck index that includes all of VisualEditor core. Right now it includes VisualEditor's index as-is, and because those patterns (e.g. ve.dm.Node) will also MW subclasses this means our category page will include MW classes under "VisualEditor (core)" (before the repo split, this was intentional). This is inevitable unless we list every class individually, or (the plan) until we move the MW subclasses out of the ve. namespace and into mw.* somewhere. Bug: 45342 Change-Id: Iff45cd555430634c9fc341fd3b177c1e0625300b 2013-12-19 23:07:19 +00:00			`[`
			`{`
			`"name": "VisualEditor (MediaWiki extension)",`
			`"groups": [`
			`{`
			`"name": "Initialization",`
			`"classes": [`
			`"ve.init.mw*",`
			`"ve.version"`
			`]`
			`},`
			`{`
			`"name": "User Interface",`
			`"classes": [`
			`"ve.ui.MW*Page"`
			`]`
			`}`
			`]`
Convince jsduck mw.Title exists Apparently we didn't have any functions taking or returning an mw.Title object, which is kind of concerning. But now that we're introducing one, we need jsduck to shut up about mw.Title not existing. Change-Id: I04028e0e3d55ed9901878cce593f857183246ab3 2014-10-28 22:44:54 +00:00			`},`
			`{`
			`"name": "Upstream (MediaWiki)",`
			`"groups": [`
			`{`
			`"name": "MediaWiki",`
			`"classes": [`
			`"mw.Title"`
			`]`
			`}`
			`]`
Use submodule for VisualEditor core * Add lib/ve. * Remove modules provided by VisualEditor core. * Update paths. * Remove VisualEditor core specific things from Gruntfile. * Remove entries from external.js already in lib/ve/.docs/external.js. * Implement build script to compose a jsduck index that includes all of VisualEditor core. Right now it includes VisualEditor's index as-is, and because those patterns (e.g. ve.dm.Node) will also MW subclasses this means our category page will include MW classes under "VisualEditor (core)" (before the repo split, this was intentional). This is inevitable unless we list every class individually, or (the plan) until we move the MW subclasses out of the ve. namespace and into mw.* somewhere. Bug: 45342 Change-Id: Iff45cd555430634c9fc341fd3b177c1e0625300b 2013-12-19 23:07:19 +00:00			`}`
			`]`