mediawiki-extensions-Discus.../tests/cases/lrm-signature/lrm-signature.json

[
	{
		"placeholderHeading": false,
		"type": "heading",
		"range": [
			"1/1/0",
			"1/1/1"
		],
		"headingLevel": 2,
		"level": 0,
		"name": "h-145.133.2.174-2017-12-28T15:32:00.000Z",
		"id": "h-joods?-2017-12-28T15:32:00.000Z",
		"warnings": [],
		"replies": [
			{
				"type": "comment",
				"timestamp": "2017-12-28T15:32:00.000Z",
				"author": "145.133.2.174",
				"range": [
					"3/0",
					"5/2/0"
				],
				"signatureRanges": [
					[
						"5/1/3",
						"5/1/8/26"
					]
				],
				"timestampRanges": [
					[
						"5/1/8/2",
						"5/1/8/26"
					]
				],
				"level": 1,
				"name": "c-145.133.2.174-2017-12-28T15:32:00.000Z",
				"id": "c-145.133.2.174-2017-12-28T15:32:00.000Z-joods?",
				"warnings": [],
				"replies": []
			}
		]
	}
]
Ignore LRM and RLM before timezone indicator They are not generated by MediaWiki, but they often appear when users sign others' unsigned comments by copy-pasting the timestamp from the history page. Add test config data for nlwiki, exported by running this in the browser console: copy( JSON.stringify( { wgArticlePath, wgNamespaceIds, wgFormattedNamespaces }, null, 2 ) + '\n' + JSON.stringify( mw.loader.moduleRegistry['ext.discussionTools.parser'].packageExports['data.json'], null, 2 ) ); Bug: T245784 Change-Id: Icbcdc5a028e9ce2cb09173f87769e525ec3082fc 2020-02-21 20:11:19 +00:00			`[`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`{`
			`"placeholderHeading": false,`
			`"type": "heading",`
			`"range": [`
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the real wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89 2022-03-09 19:32:51 +00:00			`"1/1/0",`
			`"1/1/1"`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`],`
			`"headingLevel": 2,`
			`"level": 0,`
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49 2021-02-12 19:16:13 +00:00			`"name": "h-145.133.2.174-2017-12-28T15:32:00.000Z",`
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239 2021-03-17 14:39:41 +00:00			`"id": "h-joods?-2017-12-28T15:32:00.000Z",`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`"warnings": [],`
			`"replies": [`
			`{`
			`"type": "comment",`
			`"timestamp": "2017-12-28T15:32:00.000Z",`
			`"author": "145.133.2.174",`
			`"range": [`
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the real wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89 2022-03-09 19:32:51 +00:00			`"3/0",`
			`"5/2/0"`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`],`
			`"signatureRanges": [`
			`[`
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the real wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89 2022-03-09 19:32:51 +00:00			`"5/1/3",`
			`"5/1/8/26"`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`]`
			`],`
Parser: Store timestamp ranges Change-Id: Ifcbe22011f11f4374f38b7aa346da5a96cac968c 2022-10-04 12:50:57 +00:00			`"timestampRanges": [`
			`[`
			`"5/1/8/2",`
			`"5/1/8/26"`
			`]`
			`],`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`"level": 1,`
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49 2021-02-12 19:16:13 +00:00			`"name": "c-145.133.2.174-2017-12-28T15:32:00.000Z",`
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239 2021-03-17 14:39:41 +00:00			`"id": "c-145.133.2.174-2017-12-28T15:32:00.000Z-joods?",`
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf 2021-01-26 23:55:15 +00:00			`"warnings": [],`
			`"replies": []`
			`}`
			`]`
			`}`
Ignore LRM and RLM before timezone indicator They are not generated by MediaWiki, but they often appear when users sign others' unsigned comments by copy-pasting the timestamp from the history page. Add test config data for nlwiki, exported by running this in the browser console: copy( JSON.stringify( { wgArticlePath, wgNamespaceIds, wgFormattedNamespaces }, null, 2 ) + '\n' + JSON.stringify( mw.loader.moduleRegistry['ext.discussionTools.parser'].packageExports['data.json'], null, 2 ) ); Bug: T245784 Change-Id: Icbcdc5a028e9ce2cb09173f87769e525ec3082fc 2020-02-21 20:11:19 +00:00			`]`