wikimedia/mediawiki-extensions-DiscussionTools
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/DiscussionTools synced 2024-09-29 13:26:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Discus.../tests/cases/pl-big-parsoid/pl-big-parsoid.json

3610 lines
94 KiB
JSON
Raw Normal View History

Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
[
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/0/0",
"0/1/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Kalendarium",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-29T06:23:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Stok",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/2/0",
"0/1/4/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/4/1",
"0/1/4/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Stok|2018-09-29T06:23:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-29T07:06:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Cybularny",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/6/0/0",
"0/1/6/0/3/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/6/0/1",
"0/1/6/0/3/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Cybularny|2018-09-29T07:06:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T18:20:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Zwiadowca21",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/8/0/0/0/0/0",
"0/1/8/0/0/0/12/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/1/8/0/0/0/10",
"0/1/8/0/0/0/12/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Zwiadowca21|2018-10-01T18:20:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/0/0",
"0/2/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Zmiany_interwiki_w_Wikidanych",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T01:22:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/2/0",
"0/2/6/3/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/6/0",
"0/2/6/3/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-09-30T01:22:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T07:43:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/8/0/0/0/0/0",
"0/2/8/0/0/0/7/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/8/0/0/0/4",
"0/2/8/0/0/0/7/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-09-30T07:43:00.000Z|0",
Allow updating the expected results when running PHP tests This is similar to the code we already have in JS tests, but instead of printing to the console where you have to copy-paste from, it just overwrites the files. Also, update all of the expected results by this method. Changes in the expected outputs: * In JSON files, the "warnings" are now always in the same place regardless of the type of the warning. * In all HTML files, self-closing tags now include the trailing slash, some characters are no longer encoded as entities when not necessary, and attributes may be single-quoted when that makes them shorter. * In Parsoid HTML files, the header is no longer terribly mangled. Other notes: * CommentParserTest.php: Change the output of serializeComments() to be in similar order as in JS, to reduce the diffs in this commit and because it's a better order for humans. * modifier.test.js: Remove some hacks that were working around small inconsistencies between the previous expected outputs and the actual outputs. Change-Id: I9f764640dae823321c0ac35898fa4db03f1ca364
2020-07-30 23:34:56 +00:00
"warnings": [
"Comment skips indentation level"
],
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T07:52:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/8/0/0/0/8/0/0",
"0/2/8/0/0/0/8/0/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/8/0/0/0/8/0/5",
"0/2/8/0/0/0/8/0/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-09-30T07:52:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T07:55:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/8/0/0/0/8/0/9/0/0",
"0/2/8/0/0/0/8/0/9/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/8/0/0/0/8/0/9/0/1",
"0/2/8/0/0/0/8/0/9/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 5,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-09-30T07:55:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T10:42:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "WTM",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/10/0/0",
"0/2/10/16/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/10/7",
"0/2/10/10/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
],
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/10/13",
"0/2/10/16/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|WTM|2018-09-30T10:42:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T11:09:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/0/0",
"0/2/12/0/5/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/2",
"0/2/12/0/5/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-09-30T11:09:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T16:32:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Yashaa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/6/0/0/0",
"0/2/12/0/6/0/5/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/6/0/2",
"0/2/12/0/6/0/5/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Yashaa|2018-09-30T16:32:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T21:24:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/6/0/6/0/0/0",
"0/2/12/0/6/0/6/0/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/6/0/6/0/5",
"0/2/12/0/6/0/6/0/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-09-30T21:24:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T10:18:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Yashaa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/6/0/6/0/9/0/0",
"0/2/12/0/6/0/6/0/9/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/12/0/6/0/6/0/9/0/1",
"0/2/12/0/6/0/6/0/9/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 5,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Yashaa|2018-10-01T10:18:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-30T22:17:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "WTM",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/14/0",
"0/2/14/18/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/14/15",
"0/2/14/18/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|WTM|2018-09-30T22:17:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T06:39:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Panek",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/16/0/0",
"0/2/16/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/16/0/1",
"0/2/16/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Panek|2018-10-01T06:39:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T09:52:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Panek",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/16/0/5/0/0",
"0/2/16/0/5/2/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/16/0/5/2/1",
"0/2/16/0/5/2/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Panek|2018-10-01T09:52:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T20:23:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Barcival",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/16/2/0",
"0/2/16/2/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/2/16/2/5",
"0/2/16/2/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Barcival|2018-10-01T20:23:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/0/0",
"0/3/0/4"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Hymn_Polski_a_Mazurek_Dąbrowskiego",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T13:54:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Zwiadowca21",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/2/0",
"0/3/2/15/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/2/13",
"0/3/2/15/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Zwiadowca21|2018-10-01T13:54:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-01T17:32:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piolodiusz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/4/0",
"0/3/4/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/4/3",
"0/3/4/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piolodiusz|2018-10-01T17:32:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-02T16:02:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/6/0/0",
"0/3/6/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/3/6/0/1",
"0/3/6/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-10-02T16:02:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/0/0",
"0/4/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Elx",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-03T12:51:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "MOs810",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/2/0",
"0/4/2/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/2/3",
"0/4/2/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|MOs810|2018-10-03T12:51:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-03T13:16:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Teukros",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/4/0/0",
"0/4/4/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/4/0/3",
"0/4/4/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Teukros|2018-10-03T13:16:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-03T13:59:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "MOs810",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/4/0/7/0/0",
"0/4/4/0/7/0/7/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/4/0/7/0/4",
"0/4/4/0/7/0/7/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|MOs810|2018-10-03T13:59:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-03T17:27:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Aotearoa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/4/2/0",
"0/4/4/2/4/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/4/4/2/1",
"0/4/4/2/4/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Aotearoa|2018-10-03T17:27:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/0/0",
"0/5/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Mozilla_a_Mozilla_Foundation",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-04T17:49:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "GregX21",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/2/0",
"0/5/6/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/6/1",
"0/5/6/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|GregX21|2018-10-04T17:49:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-05T15:32:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piolodiusz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/8/0/0",
"0/5/8/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/8/0/3",
"0/5/8/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piolodiusz|2018-10-05T15:32:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T07:05:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "GregX21",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/10/0/0/0/0",
"0/5/10/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/10/0/0/0/1",
"0/5/10/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|GregX21|2018-10-06T07:05:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T12:12:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Witia",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/12/0/0",
"0/5/12/0/12/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/12/0/9",
"0/5/12/0/12/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Witia|2018-10-06T12:12:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T16:18:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "GregX21",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/14/0/0/0/0",
"0/5/16/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/5/16/0/0/0/1",
"0/5/16/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|GregX21|2018-10-06T16:18:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/0/0",
"0/6/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Autoencyklopedyczność_kościołów_-_propozycja_głosowania",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T10:14:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "MOs810",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/2/0",
"0/6/2/15/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/2/12",
"0/6/2/15/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|MOs810|2018-07-29T10:14:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T10:31:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gdarin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/4/0/0",
"0/6/4/0/9/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/4/0/6",
"0/6/4/0/9/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gdarin|2018-07-29T10:31:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T10:34:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Teukros",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/4/2/0",
"0/6/4/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/4/2/1",
"0/6/4/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Teukros|2018-07-29T10:34:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T11:27:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kenraiz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/4/4/0",
"0/6/4/4/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/4/4/1",
"0/6/4/4/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kenraiz|2018-07-29T11:27:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T11:34:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gruzin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/6/0/0/0/0",
"0/6/6/0/0/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/6/0/0/0/1",
"0/6/6/0/0/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gruzin|2018-07-29T11:34:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T12:55:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Anagram16",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/6/0/2/0/0/0/0",
"0/6/6/0/2/0/0/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/6/0/2/0/0/0/1",
"0/6/6/0/2/0/0/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Anagram16|2018-07-29T12:55:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T11:52:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Adamt",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/8/0/0",
"0/6/8/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/8/0/1",
"0/6/8/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Adamt|2018-07-29T11:52:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T12:12:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Anagram16",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/8/2/0",
"0/6/8/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/8/2/1",
"0/6/8/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Anagram16|2018-07-29T12:12:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T13:37:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Hoa binh",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/8/4/0",
"0/6/8/4/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/8/4/1",
"0/6/8/4/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Hoa binh|2018-07-29T13:37:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T13:45:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Anagram16",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/10/0/0/0/0",
"0/6/10/0/0/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/10/0/0/0/1",
"0/6/10/0/0/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Anagram16|2018-07-29T13:45:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-29T16:11:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gruzin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/10/0/0/2/0",
"0/6/10/0/0/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/10/0/0/2/1",
"0/6/10/0/0/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gruzin|2018-07-29T16:11:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-30T17:54:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Zetpe0202",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/12/0/0",
"0/6/12/0/20/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/12/0/17",
"0/6/12/0/20/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Zetpe0202|2018-07-30T17:54:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-30T18:47:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gruzin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/14/0/0/0/0",
"0/6/14/0/0/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/14/0/0/0/1",
"0/6/14/0/0/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gruzin|2018-07-30T18:47:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-30T19:08:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "John Belushi",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/16/0/0",
"0/6/16/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/16/0/1",
"0/6/16/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|John Belushi|2018-07-30T19:08:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-30T19:30:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gruzin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/16/2/0",
"0/6/16/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/16/2/1",
"0/6/16/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gruzin|2018-07-30T19:30:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T08:26:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "MOs810",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/16/4/0",
"0/6/16/4/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/16/4/1",
"0/6/16/4/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|MOs810|2018-07-31T08:26:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T08:36:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "John Belushi",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/0/0",
"0/6/18/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/0/1",
"0/6/18/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|John Belushi|2018-07-31T08:36:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T14:56:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gruzin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/2/0",
"0/6/18/0/0/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/2/1",
"0/6/18/0/0/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gruzin|2018-07-31T14:56:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T15:21:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Teukros",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/4/0",
"0/6/18/0/0/4/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/4/1",
"0/6/18/0/0/4/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Teukros|2018-07-31T15:21:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T16:44:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Malarz pl",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/6/0",
"0/6/18/0/0/6/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/6/1",
"0/6/18/0/0/6/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Malarz pl|2018-07-31T16:44:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T17:50:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Zala",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/6/5/0/0",
"0/6/18/0/0/6/5/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/6/5/0/1",
"0/6/18/0/0/6/5/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Zala|2018-07-31T17:50:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-07-31T22:05:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Adamt",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/8/0",
"0/6/18/0/0/8/4/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/0/8/1",
"0/6/18/0/0/8/4/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Adamt|2018-07-31T22:05:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-08-01T18:20:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "John Belushi",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/2/0/0/0/0",
"0/6/18/0/2/0/0/0/11/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/18/0/2/0/0/0/8",
"0/6/18/0/2/0/0/0/11/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|John Belushi|2018-08-01T18:20:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-08-06T14:08:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "KamilK7",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/20/0/0",
"0/6/20/0/4/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/20/0/1",
"0/6/20/0/4/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|KamilK7|2018-08-06T14:08:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-08-13T22:43:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Cz ja",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/22/0",
"0/6/22/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/22/1",
"0/6/22/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
],
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/22/5",
"0/6/22/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Cz ja|2018-08-13T22:43:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-08-14T07:07:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Malarz pl",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/24/0/0",
"0/6/24/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/24/0/3",
"0/6/24/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Malarz pl|2018-08-14T07:07:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-08-31T15:59:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "BasileusAutokratorPL",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/26/0",
"0/6/26/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/26/1",
"0/6/26/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|BasileusAutokratorPL|2018-08-31T15:59:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-08T16:10:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/28/0/0/0",
"0/6/28/0/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/28/0/5",
"0/6/28/0/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-09-08T16:10:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-09-09T15:15:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "BasileusAutokratorPL",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/30/0",
"0/6/30/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/30/1",
"0/6/30/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|BasileusAutokratorPL|2018-09-09T15:15:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-08T09:34:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Alan ffm",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/32/0/0",
"0/6/32/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/6/32/0/1",
"0/6/32/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Alan ffm|2018-10-08T09:34:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/7/0/0",
"0/7/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Zbrodnie_oddziałów_Ludowej_Straży_Bezpieczeństwa",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-09T20:26:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/7/2/0",
"0/7/2/8/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/7/2/5",
"0/7/2/8/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-10-09T20:26:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-11T12:15:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kriis bis",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/7/4/0/0",
"0/7/4/0/14/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/7/4/0/11",
"0/7/4/0/14/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kriis bis|2018-10-11T12:15:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/0/0",
"0/8/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Sekcja_Literatura",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-10T19:51:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/2/0",
"0/8/2/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/2/5",
"0/8/2/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-10T19:51:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-10T21:52:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/4/0/0",
"0/8/4/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/4/0/1",
"0/8/4/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-10T21:52:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-11T08:12:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/6/0/0",
"0/8/6/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/6/0/1",
"0/8/6/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-11T08:12:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-11T12:44:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Henryk Tannhäuser",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/6/2/0",
"0/8/6/2/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/8/6/2/5",
"0/8/6/2/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Henryk Tannhäuser|2018-10-11T12:44:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/9/0/0",
"0/9/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Jerzy_Mrozowicki",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-11T20:46:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "WTM",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/9/2/0",
"0/9/2/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/9/2/3",
"0/9/2/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|WTM|2018-10-11T20:46:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-12T07:11:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kriis bis",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/9/4/0/0",
"0/9/4/0/9/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/9/4/0/6",
"0/9/4/0/9/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kriis bis|2018-10-12T07:11:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/0/0",
"0/10/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|„Cyklon_B”_czy_„cyklon_B”?",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T12:50:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Jacek555",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/2/0",
"0/10/2/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/2/3",
"0/10/2/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Jacek555|2018-10-06T12:50:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T16:35:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/4/0/0",
"0/10/4/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/4/0/1",
"0/10/4/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-06T16:35:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T17:18:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/0/0",
"0/10/6/0/8/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/0/5",
"0/10/6/0/8/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-10-06T17:18:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-06T17:36:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Matrek",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/2/0",
"0/10/6/2/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/2/1",
"0/10/6/2/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Matrek|2018-10-06T17:36:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T08:20:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Dreamcatcher25",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/4/0",
"0/10/6/4/7/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/4/4",
"0/10/6/4/7/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Dreamcatcher25|2018-10-07T08:20:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T16:04:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Matrek",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/4/8/0/0/0/0/0",
"0/10/6/4/8/0/0/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/4/8/0/0/0/3",
"0/10/6/4/8/0/0/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Matrek|2018-10-07T16:04:00.000Z|0",
Stop printing console warnings It was useful when I was debugging those parts of the code, but now it's usually annoying. The warnings can still sometimes be useful for understanding how the tool parses some discussion, though. To keep that functionality, add displaying warnings for each comment in the debug mode. Change-Id: I2d218a8a394f179bcc0990ff988a0567c275ccf2
2020-05-13 18:23:48 +00:00
"warnings": [
"Comment skips indentation level"
Allow updating the expected results when running PHP tests This is similar to the code we already have in JS tests, but instead of printing to the console where you have to copy-paste from, it just overwrites the files. Also, update all of the expected results by this method. Changes in the expected outputs: * In JSON files, the "warnings" are now always in the same place regardless of the type of the warning. * In all HTML files, self-closing tags now include the trailing slash, some characters are no longer encoded as entities when not necessary, and attributes may be single-quoted when that makes them shorter. * In Parsoid HTML files, the header is no longer terribly mangled. Other notes: * CommentParserTest.php: Change the output of serializeComments() to be in similar order as in JS, to reduce the diffs in this commit and because it's a better order for humans. * modifier.test.js: Remove some hacks that were working around small inconsistencies between the previous expected outputs and the actual outputs. Change-Id: I9f764640dae823321c0ac35898fa4db03f1ca364
2020-07-30 23:34:56 +00:00
],
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T11:43:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/4/8/2/0",
"0/10/6/4/8/2/4/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/4/8/2/1",
"0/10/6/4/8/2/4/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-10-07T11:43:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T16:27:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/0",
"0/10/6/6/8/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/5",
"0/10/6/6/8/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-10-07T16:27:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T16:34:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Matrek",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/0",
"0/10/6/6/9/0/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/1",
"0/10/6/6/9/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
],
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/5",
"0/10/6/6/9/0/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Matrek|2018-10-07T16:34:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T16:53:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/9/0/0",
"0/10/6/6/9/0/9/0/8/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/9/0/5",
"0/10/6/6/9/0/9/0/8/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-10-07T16:53:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T18:49:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/9/0/9/0/0",
"0/10/6/6/9/0/9/0/9/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/0/9/0/9/0/3",
"0/10/6/6/9/0/9/0/9/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 5,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-07T18:49:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-08T16:33:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Jacek555",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/2/0/0",
"0/10/6/6/9/2/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/6/9/2/3",
"0/10/6/6/9/2/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Jacek555|2018-10-08T16:33:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T16:32:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gruzin",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/8/0",
"0/10/6/8/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/8/1",
"0/10/6/8/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gruzin|2018-10-07T16:32:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-07T18:00:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Lesław Zimny",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/10/0",
"0/10/6/10/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/6/10/3",
"0/10/6/10/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Lesław Zimny|2018-10-07T18:00:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-08T08:01:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Alan ffm",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/8/0/0/0/0",
"0/10/8/0/0/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/8/0/0/0/3",
"0/10/8/0/0/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Alan ffm|2018-10-08T08:01:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-08T16:33:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Jacek555",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/8/0/2/0/0/0/0",
"0/10/8/0/2/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/8/0/2/0/0/0/1",
"0/10/8/0/2/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Jacek555|2018-10-08T16:33:00.000Z|1",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-08T16:33:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Jacek555",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/10/0/0",
"0/10/10/0/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/10/0/5",
"0/10/10/0/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Jacek555|2018-10-08T16:33:00.000Z|2",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T17:40:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wostr",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/10/2/0/0",
"0/10/10/2/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/10/2/5",
"0/10/10/2/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wostr|2018-10-16T17:40:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T17:53:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Jacek555",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/12/0/0",
"0/10/12/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/10/12/0/3",
"0/10/12/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Jacek555|2018-10-16T17:53:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/0/0",
"0/11/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Przypisy_do_ebooków._Co_z_numerami_stron?",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T10:55:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Pawelmhm",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/2/0",
"0/11/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/2/1",
"0/11/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Pawelmhm|2018-10-16T10:55:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T11:30:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ironupiwada",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/0/0",
"0/11/4/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/0/3",
"0/11/4/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ironupiwada|2018-10-16T11:30:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T12:01:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Pawelmhm",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/2/0/0",
"0/11/4/2/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/2/3",
"0/11/4/2/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Pawelmhm|2018-10-16T12:01:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T12:14:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Tomasz Raburski",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/4/0",
"0/11/4/4/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/4/1",
"0/11/4/4/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Tomasz Raburski|2018-10-16T12:14:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T13:48:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/6/0",
"0/11/4/6/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/6/1",
"0/11/4/6/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-16T13:48:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-16T14:57:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ironupiwada",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/6/5/0/0",
"0/11/4/6/5/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/6/5/0/1",
"0/11/4/6/5/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ironupiwada|2018-10-16T14:57:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-17T06:56:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/6/5/0/5/0/0",
"0/11/4/6/5/0/5/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/11/4/6/5/0/5/0/3",
"0/11/4/6/5/0/5/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-17T06:56:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/12/0/0",
"0/12/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Nazewnictwo_planetoid",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-17T06:39:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gżdacz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/12/2/0",
"0/12/2/9/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/12/2/6",
"0/12/2/9/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gżdacz|2018-10-17T06:39:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-17T07:16:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Michał Rosa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/12/4/0/0",
"0/12/4/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/12/4/0/3",
"0/12/4/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Michał Rosa|2018-10-17T07:16:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/0/0",
"0/13/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Czy_ten_szablon_powinien_istnieć?",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-11T17:25:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/2/0/0/0",
"0/13/2/10/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/2/7",
"0/13/2/10/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-11T17:25:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-12T11:17:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Bobek321",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/4/0/0",
"0/13/4/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/4/0/3",
"0/13/4/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Bobek321|2018-10-12T11:17:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-12T18:22:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/6/0/0/0/0",
"0/13/6/0/0/0/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/6/0/0/0/5",
"0/13/6/0/0/0/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-12T18:22:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-12T18:51:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kenraiz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/6/0/0/0/9/0/0",
"0/13/6/0/0/0/9/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/6/0/0/0/9/0/3",
"0/13/6/0/0/0/9/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kenraiz|2018-10-12T18:51:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-15T22:47:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ented",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/8/0/0",
"0/13/8/0/7/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/8/0/4",
"0/13/8/0/7/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ented|2018-10-15T22:47:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-17T19:08:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Bobek321",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/8/2/0",
"0/13/8/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/8/2/1",
"0/13/8/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Bobek321|2018-10-17T19:08:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-17T19:25:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/10/0/0/0/0",
"0/13/10/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/10/0/0/0/1",
"0/13/10/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-17T19:25:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-17T19:49:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Malarz pl",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/10/2/0",
"0/13/10/2/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/13/10/2/3",
"0/13/10/2/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Malarz pl|2018-10-17T19:49:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/0/0",
"0/14/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Pytanie_dotyczące_artykułów_o_czasopismach._Czy_ta_sama_nazwa_czasopisma_wydawanego_w_różnych_okresach_czasowych_zasługuje_na_to_samo_hasło?",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T10:29:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Pawelmhm",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/2/0",
"0/14/2/14/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/2/11",
"0/14/2/14/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Pawelmhm|2018-10-18T10:29:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T11:05:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Tomasz Raburski",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/4/0/0",
"0/14/4/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/4/0/1",
"0/14/4/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Tomasz Raburski|2018-10-18T11:05:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T12:04:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/4/2/0",
"0/14/4/2/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/14/4/2/3",
"0/14/4/2/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-18T12:04:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/15/0/0",
"0/15/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Tło_w_komórce",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-19T01:41:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Demkoff",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/15/2/0/0/0",
"0/15/6/0/10/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/15/6/0/7",
"0/15/6/0/10/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Only detect comments with real signatures Consequences of this are visible in the test cases: * (en) Tech News posts are not detected. Examples: "21:22, 1 July 2019 (UTC)", "21:42, 29 July 2019 (UTC)" * (en) Comments by users who customize the timestamp are not detected. Examples: "10:49, 28 June 2019 (UTC)", "21:34, 14 July 2019 (UTC)" * (en) Comments with signatures missing a username are not detected. This sometimes happens if a comment is accidentally signed with '~~~~~' (five tildes), which only inserts the timestamp. Examples: "17:17, 27 July 2019 (UTC)", "10:25, 29 July 2019 (UTC)" * (pl) A lone timestamp at the beginning of a thread is not detected. It's not part of a post, it was added to aid automatic archiving. Example: "21:03, 18 paź 2018 (CET)" Bug: T245692 Change-Id: I0767bb239a1800f2e538917b5995fc4f0fa4d043
2020-02-20 22:06:17 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Demkoff|2018-10-19T01:41:00.000Z|0",
Stop printing console warnings It was useful when I was debugging those parts of the code, but now it's usually annoying. The warnings can still sometimes be useful for understanding how the tool parses some discussion, though. To keep that functionality, add displaying warnings for each comment in the debug mode. Change-Id: I2d218a8a394f179bcc0990ff988a0567c275ccf2
2020-05-13 18:23:48 +00:00
"warnings": [
"Comment skips indentation level"
Allow updating the expected results when running PHP tests This is similar to the code we already have in JS tests, but instead of printing to the console where you have to copy-paste from, it just overwrites the files. Also, update all of the expected results by this method. Changes in the expected outputs: * In JSON files, the "warnings" are now always in the same place regardless of the type of the warning. * In all HTML files, self-closing tags now include the trailing slash, some characters are no longer encoded as entities when not necessary, and attributes may be single-quoted when that makes them shorter. * In Parsoid HTML files, the header is no longer terribly mangled. Other notes: * CommentParserTest.php: Change the output of serializeComments() to be in similar order as in JS, to reduce the diffs in this commit and because it's a better order for humans. * modifier.test.js: Remove some hacks that were working around small inconsistencies between the previous expected outputs and the actual outputs. Change-Id: I9f764640dae823321c0ac35898fa4db03f1ca364
2020-07-30 23:34:56 +00:00
],
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/0/0",
"0/16/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Ułamki",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-02T20:26:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Paweł Ziemian",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/2/0",
"0/16/2/18/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/2/15",
"0/16/2/18/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Paweł Ziemian|2018-10-02T20:26:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-02T22:16:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Matma Rex",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/4/0/0",
"0/16/4/0/6/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/4/0/3",
"0/16/4/0/6/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Matma Rex|2018-10-02T22:16:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-19T12:09:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ashaio",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/6/0",
"0/16/6/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/6/5",
"0/16/6/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ashaio|2018-10-19T12:09:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-19T20:23:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Paweł Ziemian",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/8/0/0",
"0/16/8/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/16/8/0/3",
"0/16/8/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Paweł Ziemian|2018-10-19T20:23:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/0/0",
"0/17/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|\"To_źródło_nie_zostało_użyte_do_napisania_tych_treści\"",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T13:45:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/2/0",
"0/17/2/12/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/2/9",
"0/17/2/12/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-18T13:45:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T15:07:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kenraiz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/0/0",
"0/17/4/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/0/1",
"0/17/4/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kenraiz|2018-10-18T15:07:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T17:12:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/0/5/0/0",
"0/17/4/0/5/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/0/5/0/3",
"0/17/4/0/5/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-18T17:12:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T15:24:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "WTM",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/2/0",
"0/17/4/2/7/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/2/4",
"0/17/4/2/7/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|WTM|2018-10-18T15:24:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T17:11:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/2/8/0/0",
"0/17/4/2/8/0/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/4/2/8/0/5",
"0/17/4/2/8/0/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-18T17:11:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T18:39:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ented",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/0/0/0",
"0/17/6/0/13/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/0/10",
"0/17/6/0/13/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ented|2018-10-18T18:39:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-18T18:45:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kenraiz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/0",
"0/17/6/2/11/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/8",
"0/17/6/2/11/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kenraiz|2018-10-18T18:45:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-19T19:10:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/12/0/0/0",
"0/17/6/2/12/0/16/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/12/0/13",
"0/17/6/2/12/0/16/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-19T19:10:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-19T19:21:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kenraiz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/12/0/17/0/0",
"0/17/6/2/12/0/17/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/12/0/17/0/1",
"0/17/6/2/12/0/17/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kenraiz|2018-10-19T19:21:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-21T12:40:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/12/0/17/2/0/0",
"0/17/6/2/12/0/17/2/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/17/6/2/12/0/17/2/5",
"0/17/6/2/12/0/17/2/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-21T12:40:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/0/0",
"0/18/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Tytuł_filmu",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-21T12:45:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Czyz1",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/2/0",
"0/18/2/13/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/2/10",
"0/18/2/13/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Czyz1|2018-10-21T12:45:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-21T17:12:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Teukros",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/0/0",
"0/18/4/0/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/0/5",
"0/18/4/0/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Teukros|2018-10-21T17:12:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-21T19:09:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Czyz1",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/0/9/0/0",
"0/18/4/0/9/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/0/9/0/1",
"0/18/4/0/9/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Czyz1|2018-10-21T19:09:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-21T19:25:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Mike210381",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/2/0/0",
"0/18/4/2/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/2/5",
"0/18/4/2/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Mike210381|2018-10-21T19:25:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-22T15:26:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Aotearoa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/4/0",
"0/18/4/4/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/4/5",
"0/18/4/4/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Aotearoa|2018-10-22T15:26:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T10:29:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Czyz1",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/4/9/0/0",
"0/18/4/4/9/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/4/9/0/3",
"0/18/4/4/9/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Czyz1|2018-10-23T10:29:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T16:44:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/6/0",
"0/18/4/6/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/18/4/6/1",
"0/18/4/6/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-10-23T16:44:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/19/0/0",
"0/19/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Osiedla",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T19:16:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Stok",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/19/2/0",
"0/19/6/3/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/19/6/0",
"0/19/6/3/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Stok|2018-10-23T19:16:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/20/0/0",
"0/20/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Pokolenie_Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T21:59:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/20/2/0",
"0/20/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/20/2/1",
"0/20/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-10-23T21:59:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/21/0/0",
"0/21/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Zofia_Więcławówna_-_korekta_umiejscowienia_grafiki",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T07:59:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Agrezt",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/21/2/0",
"0/21/4/3/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/21/4/0",
"0/21/4/3/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Agrezt|2018-10-25T07:59:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T08:15:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/21/6/0/0",
"0/21/6/0/11/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/21/6/0/8",
"0/21/6/0/11/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-25T08:15:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/22/0/0",
"0/22/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Bitwa_pod_Brunete",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-14T19:29:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Andrzej1993",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/22/2/0",
"0/22/10/3/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/22/10/0",
"0/22/10/3/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Andrzej1993|2018-10-14T19:29:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T12:59:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "KamilK7",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/22/12/0/0/0",
"0/22/12/0/9/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/22/12/0/6",
"0/22/12/0/9/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|KamilK7|2018-10-25T12:59:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/23/0/0",
"0/23/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Podwójne_nazwiska_w_infoboksach",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T20:40:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Karol Szapsza",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/23/2/0",
"0/23/2/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/23/2/3",
"0/23/2/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Karol Szapsza|2018-10-25T20:40:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/0/0",
"0/24/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Facebook_jako_źródło",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T16:01:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/2/0",
"0/24/2/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/2/3",
"0/24/2/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-23T16:01:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T16:43:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Eurohunter",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/4/0/0",
"0/24/4/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/4/0/1",
"0/24/4/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Eurohunter|2018-10-23T16:43:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T16:46:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Tokyotown8",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/6/0/0",
"0/24/6/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/6/0/1",
"0/24/6/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Tokyotown8|2018-10-23T16:46:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T16:52:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/0",
"0/24/8/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/1",
"0/24/8/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-23T16:52:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T17:16:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Tokyotown8",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/5/0/0",
"0/24/8/0/0/0/5/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/5/0/1",
"0/24/8/0/0/0/5/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Tokyotown8|2018-10-23T17:16:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T17:40:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Mpn",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/5/2/0",
"0/24/8/0/0/0/5/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/5/2/1",
"0/24/8/0/0/0/5/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 4,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Mpn|2018-10-23T17:40:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T17:44:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Szoltys",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/5/2/5/0/0",
"0/24/8/0/0/0/5/2/5/0/2/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/8/0/0/0/5/2/5/0/1",
"0/24/8/0/0/0/5/2/5/0/2/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 5,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Szoltys|2018-10-23T17:44:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T17:56:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "109.233.47.132",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/0/0",
"0/24/10/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/0/1",
"0/24/10/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|109.233.47.132|2018-10-23T17:56:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T20:50:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Panek",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/2/0",
"0/24/10/2/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/2/1",
"0/24/10/2/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Panek|2018-10-23T20:50:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-23T21:36:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Kenraiz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/4/0",
"0/24/10/4/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/4/1",
"0/24/10/4/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Kenraiz|2018-10-23T21:36:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T12:09:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "KamilK7",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/6/0",
"0/24/10/6/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/10/6/1",
"0/24/10/6/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|KamilK7|2018-10-25T12:09:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T17:14:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "BasileusAutokratorPL",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/12/0",
"0/24/12/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/12/1",
"0/24/12/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|BasileusAutokratorPL|2018-10-25T17:14:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T18:43:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Żyrafał",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/14/0/0",
"0/24/14/0/10/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/14/0/7",
"0/24/14/0/10/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Żyrafał|2018-10-25T18:43:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T05:36:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piolodiusz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/16/0/0/0",
"0/24/16/0/8/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/16/0/5",
"0/24/16/0/8/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piolodiusz|2018-10-26T05:36:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T16:09:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Żyrafał",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/16/0/9/0/0/0",
"0/24/16/0/9/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/16/0/9/0/3",
"0/24/16/0/9/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Żyrafał|2018-10-26T16:09:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T16:13:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Michalwadas",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/18/0/0",
"0/24/18/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/24/18/0/1",
"0/24/18/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Michalwadas|2018-10-26T16:13:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/25/0/0",
"0/25/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Wyśrodkowanie_tekstu",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T17:17:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "WTM",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/25/2/0",
"0/25/4/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/25/4/0/3",
"0/25/4/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|WTM|2018-10-26T17:17:00.000Z|0",
Stop printing console warnings It was useful when I was debugging those parts of the code, but now it's usually annoying. The warnings can still sometimes be useful for understanding how the tool parses some discussion, though. To keep that functionality, add displaying warnings for each comment in the debug mode. Change-Id: I2d218a8a394f179bcc0990ff988a0567c275ccf2
2020-05-13 18:23:48 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/0/0",
"0/26/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Reprezentacja_Polski_w_piłce_nożnej_mężczyzn",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T17:07:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "BasileusAutokratorPL",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/1/0",
"0/26/4/9/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/4/6",
"0/26/4/9/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|BasileusAutokratorPL|2018-10-26T17:07:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T17:27:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/0/0",
"0/26/6/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/0/1",
"0/26/6/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-26T17:27:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T20:19:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Mitrovitz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/2/0",
"0/26/6/2/12/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/2/9",
"0/26/6/2/12/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Mitrovitz|2018-10-26T20:19:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T21:21:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Vinsinna",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/2/13/0/0",
"0/26/6/2/13/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/2/13/0/3",
"0/26/6/2/13/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Vinsinna|2018-10-26T21:21:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T22:01:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Piotr967",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/4/0",
"0/26/6/4/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/4/1",
"0/26/6/4/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
],
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/4/5",
"0/26/6/4/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Piotr967|2018-10-26T22:01:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-26T22:10:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ented",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/6/0",
"0/26/6/6/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/26/6/6/1",
"0/26/6/6/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ented|2018-10-26T22:10:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/0/0",
"0/27/0/1"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Ikonki_w_infoboksach",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-20T18:23:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Wiktoryn",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/2/0",
"0/27/2/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/2/3",
"0/27/2/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Wiktoryn|2018-10-20T18:23:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-28T17:53:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Malarz pl",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/4/0/0",
"0/27/4/0/6/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/4/0/3",
"0/27/4/0/6/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Malarz pl|2018-10-28T17:53:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-28T18:50:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Elfhelm",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/4/2/0",
"0/27/4/2/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/27/4/2/1",
"0/27/4/2/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Elfhelm|2018-10-28T18:50:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/0/0",
"0/28/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|{{Tenisista_infobox}}",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-29T08:12:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Arvedui89",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/2/0",
"0/28/2/6/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/2/3",
"0/28/2/6/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Arvedui89|2018-10-29T08:12:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-29T10:20:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/4/0/0",
"0/28/4/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/4/0/1",
"0/28/4/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-29T10:20:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-29T10:49:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Malarz pl",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/4/2/0/0/0",
"0/28/4/2/7/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/28/4/2/4",
"0/28/4/2/7/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Malarz pl|2018-10-29T10:49:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/0/0",
"0/29/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Encyklopedyczność_biogramów_harcerskich",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-24T01:36:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Smyrwa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/2/0",
"0/29/22/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/22/1",
"0/29/22/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Smyrwa|2018-10-24T01:36:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-24T06:35:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Gżdacz",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/24/0/0",
"0/29/24/0/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/24/0/1",
"0/29/24/0/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Gżdacz|2018-10-24T06:35:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-24T15:14:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Pbk",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/24/2/0",
"0/29/30/10/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/30/1",
"0/29/30/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
],
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/30/7",
"0/29/30/10/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Pbk|2018-10-24T15:14:00.000Z|0",
Stop printing console warnings It was useful when I was debugging those parts of the code, but now it's usually annoying. The warnings can still sometimes be useful for understanding how the tool parses some discussion, though. To keep that functionality, add displaying warnings for each comment in the debug mode. Change-Id: I2d218a8a394f179bcc0990ff988a0567c275ccf2
2020-05-13 18:23:48 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-30T14:58:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Smyrwa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/32/0/0/0/0",
"0/29/34/0/0/0/8/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/34/0/0/0/5",
"0/29/34/0/0/0/8/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Smyrwa|2018-10-30T14:58:00.000Z|0",
Stop printing console warnings It was useful when I was debugging those parts of the code, but now it's usually annoying. The warnings can still sometimes be useful for understanding how the tool parses some discussion, though. To keep that functionality, add displaying warnings for each comment in the debug mode. Change-Id: I2d218a8a394f179bcc0990ff988a0567c275ccf2
2020-05-13 18:23:48 +00:00
"warnings": [
"Comment skips indentation level"
Allow updating the expected results when running PHP tests This is similar to the code we already have in JS tests, but instead of printing to the console where you have to copy-paste from, it just overwrites the files. Also, update all of the expected results by this method. Changes in the expected outputs: * In JSON files, the "warnings" are now always in the same place regardless of the type of the warning. * In all HTML files, self-closing tags now include the trailing slash, some characters are no longer encoded as entities when not necessary, and attributes may be single-quoted when that makes them shorter. * In Parsoid HTML files, the header is no longer terribly mangled. Other notes: * CommentParserTest.php: Change the output of serializeComments() to be in similar order as in JS, to reduce the diffs in this commit and because it's a better order for humans. * modifier.test.js: Remove some hacks that were working around small inconsistencies between the previous expected outputs and the actual outputs. Change-Id: I9f764640dae823321c0ac35898fa4db03f1ca364
2020-07-30 23:34:56 +00:00
],
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T10:50:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Andrzei111",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/36/0/0",
"0/29/36/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/36/0/3",
"0/29/36/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Andrzei111|2018-10-25T10:50:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-30T14:58:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Smyrwa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/38/0/0/0/0",
"0/29/38/0/0/0/6/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/38/0/0/0/3",
"0/29/38/0/0/0/6/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Smyrwa|2018-10-30T14:58:00.000Z|1",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T10:59:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Felis domestica",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/40/0/0",
"0/29/40/0/6/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/40/0/3",
"0/29/40/0/6/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Felis domestica|2018-10-25T10:59:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-25T20:03:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "BasileusAutokratorPL",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/42/0",
"0/29/42/4/27"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/42/1",
"0/29/42/4/27"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|BasileusAutokratorPL|2018-10-25T20:03:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-30T14:58:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Smyrwa",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/44/0/0/0/0",
"0/29/44/0/0/0/4/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/29/44/0/0/0/1",
"0/29/44/0/0/0/4/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 3,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Smyrwa|2018-10-30T14:58:00.000Z|2",
Stop printing console warnings It was useful when I was debugging those parts of the code, but now it's usually annoying. The warnings can still sometimes be useful for understanding how the tool parses some discussion, though. To keep that functionality, add displaying warnings for each comment in the debug mode. Change-Id: I2d218a8a394f179bcc0990ff988a0567c275ccf2
2020-05-13 18:23:48 +00:00
"warnings": [
"Comment skips indentation level"
Allow updating the expected results when running PHP tests This is similar to the code we already have in JS tests, but instead of printing to the console where you have to copy-paste from, it just overwrites the files. Also, update all of the expected results by this method. Changes in the expected outputs: * In JSON files, the "warnings" are now always in the same place regardless of the type of the warning. * In all HTML files, self-closing tags now include the trailing slash, some characters are no longer encoded as entities when not necessary, and attributes may be single-quoted when that makes them shorter. * In Parsoid HTML files, the header is no longer terribly mangled. Other notes: * CommentParserTest.php: Change the output of serializeComments() to be in similar order as in JS, to reduce the diffs in this commit and because it's a better order for humans. * modifier.test.js: Remove some hacks that were working around small inconsistencies between the previous expected outputs and the actual outputs. Change-Id: I9f764640dae823321c0ac35898fa4db03f1ca364
2020-07-30 23:34:56 +00:00
],
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
},
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "heading",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/30/0/0",
"0/30/0/2"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f
2020-10-01 19:36:11 +00:00
"headingLevel": 2,
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 0,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "h|Szablon?_do_zrobienia?",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-31T13:57:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Ciacho5",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/30/2/0",
"0/30/2/9/26"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/30/2/6",
"0/30/2/9/26"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 1,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Ciacho5|2018-10-31T13:57:00.000Z|0",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"replies": [
{
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"type": "comment",
"timestamp": "2018-10-31T14:55:00.000Z",
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
"author": "Malarz pl",
"range": [
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/30/4/0/0",
"0/30/4/0/4/25"
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
],
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
"signatureRanges": [
[
tests: Fix computing ranges in Parsoid documents In JS tests, we load the documents via mw.template, which apparently causes the <html>, <head> and <body> tags to disappear, resulting in the ranges not matching in PHP tests (and the real document). Put in a big hack that makes them match, and update the JSON files. Change-Id: I8194752cd5f82c3716c99e76a37226af5d4a0ec1
2020-05-13 20:19:43 +00:00
"0/30/4/0/1",
"0/30/4/0/4/25"
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac
2020-03-04 16:14:47 +00:00
]
],
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"level": 2,
Allow headings to have IDs Previously, only comments could have IDs, because we only needed IDs for replying. But we might also use them for notifications soon. Bug: T264478 Change-Id: I1bcad02bf17ab54bc5028a959543c10f0430836b
2020-09-22 23:05:25 +00:00
"id": "c|Malarz pl|2018-10-31T14:55:00.000Z|0",
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
"replies": []
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
Document how to update the test JSON files (And rebuild them using this method, the properties are in different order, it's actually nice for readability to have 'replies' last) Change-Id: Ib586e1081fa36cb9125db1b0b1d41f092350641c
2019-11-24 16:28:01 +00:00
]
Integration tests for parsing Tests that handle a specific case and describe what they are testing would be nice… but tests that just document the current status to avoid regressions are also okay and easier to add. Change-Id: I0b3530ae0e77de70932aaf623f5290d1876699a0
2019-10-24 12:59:42 +00:00
}
]
Reference in a new issue Copy permalink