wikimedia/mediawiki-extensions-DiscussionTools
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/DiscussionTools synced 2024-12-21 04:15:36 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Discus.../tests/cases/it-unsigned-parsoid/it-unsigned-parsoid.json

2643 lines
64 KiB
JSON
Raw Normal View History

Add tests covering it.wp unsigned comment template Bug: T268178 Bug: T268589 Change-Id: Icd353275b3b8191eddbff4d72984a8c2c8e6cdd6
2020-11-25 00:06:56 +00:00
[
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"1/0/0",
"1/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Depoggial-2020-11-06T18:25:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Biografia_di_Gino_Coletti-2020-11-06T18:25:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-06T18:25:00.000Z",
"author": "Depoggial",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"1/2/0",
"1/2/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"1/2/1",
"1/2/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Depoggial-2020-11-06T18:25:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Depoggial-2020-11-06T18:25:00.000Z-Biografia_di_Gino_Coletti",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-13T21:16:00.000Z",
"author": "Depoggial",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"1/4/0/0/0/0",
"1/4/0/0/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"1/4/0/0/2/1",
"1/4/0/0/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Depoggial-2020-11-13T21:16:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Depoggial-2020-11-13T21:16:00.000Z-Depoggial-2020-11-06T18:25:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment skips indentation level"
],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/0/0",
"2/0/2"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Componenti_standard_per_macchine-2020-11-13T07:33:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Salvare_anteprima_pagina_senza_pubblicarla_-_Componenti_standard_per_macchine/Sa-2020-11-13T07:33:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-13T07:33:00.000Z",
"author": "Componenti standard per macchine",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/2/0",
"2/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/2/1/2/3",
"2/2/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Componenti_standard_per_macchine-2020-11-13T07:33:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Componenti_standard_per_macchine-2020-11-13T07:33:00.000Z-Salvare_anteprima_pagina_senza_pubblicarla_-_Componenti_standard_per_macchine/Sa",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-13T07:36:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/4/0/0/0/0",
"2/4/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/4/0/2",
"2/4/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-13T07:36:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-13T07:36:00.000Z-Componenti_standard_per_macchine-2020-11-13T07:33:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-13T10:19:00.000Z",
"author": "87.9.146.3",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/4/0/4/0/0",
"2/4/0/4/2/12/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"2/4/0/4/2/9",
"2/4/0/4/2/12/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.9.146.3-2020-11-13T10:19:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.9.146.3-2020-11-13T10:19:00.000Z-ValeJappo-2020-11-13T07:36:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/0/0",
"3/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Giuliano_Caputi-2020-11-13T11:28:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Vorrei_cambiare_ed_aggiungere_foto_sulla_mia_pagina-2020-11-13T11:28:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-13T11:28:00.000Z",
"author": "Giuliano Caputi",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/2/0",
"3/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/2/1/2/3",
"3/2/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Giuliano_Caputi-2020-11-13T11:28:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Giuliano_Caputi-2020-11-13T11:28:00.000Z-Vorrei_cambiare_ed_aggiungere_foto_sulla_mia_pagina",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-14T14:45:00.000Z",
"author": "Enzo Encius",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/4/0/0",
"3/4/0/10/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/4/0/9",
"3/4/0/10/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Enzo_Encius-2020-11-14T14:45:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Enzo_Encius-2020-11-14T14:45:00.000Z-Giuliano_Caputi-2020-11-13T11:28:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-14T14:46:00.000Z",
"author": "Enzo Encius",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/4/0/11/0/0",
"3/4/0/11/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"3/4/0/11/0/3",
"3/4/0/11/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Enzo_Encius-2020-11-14T14:46:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Enzo_Encius-2020-11-14T14:46:00.000Z-Enzo_Encius-2020-11-14T14:45:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"4/0/0",
"4/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-87.9.146.3-2020-11-14T18:32:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-voce_riguardante_un_centro_abitato-2020-11-14T18:32:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-14T18:32:00.000Z",
"author": "87.9.146.3",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"4/2/0",
"4/4/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"4/4/2/5",
"4/4/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.9.146.3-2020-11-14T18:32:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.9.146.3-2020-11-14T18:32:00.000Z-voce_riguardante_un_centro_abitato",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"5/0/0",
"5/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-AstrolabioD-2020-11-14T19:52:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Creare_pagina_di_uno_scrittore_argentino-2020-11-14T19:52:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-14T19:52:00.000Z",
"author": "AstrolabioD",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"5/2/0",
"5/4/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"5/4/1",
"5/4/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-AstrolabioD-2020-11-14T19:52:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-AstrolabioD-2020-11-14T19:52:00.000Z-Creare_pagina_di_uno_scrittore_argentino",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-15T11:35:00.000Z",
"author": "Mtarch11",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"5/6/0/0",
"5/6/0/16/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"5/6/0/11",
"5/6/0/16/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Mtarch11-2020-11-15T11:35:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Mtarch11-2020-11-15T11:35:00.000Z-AstrolabioD-2020-11-14T19:52:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/0/0",
"6/0/2"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Mamasaura-2020-11-16T13:38:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Assenza_del_tasto_\"sposta\"_dalla_mia_sandbox-2020-11-16T13:38:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T13:38:00.000Z",
"author": "Mamasaura",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/2/0",
"6/2/4/36"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/2/1",
"6/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Mamasaura-2020-11-16T13:38:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Mamasaura-2020-11-16T13:38:00.000Z-Assenza_del_tasto_\"sposta\"_dalla_mia_sandbox",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T14:33:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/4/0/0",
"6/6/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/1",
"6/6/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-16T14:33:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-16T14:33:00.000Z-Mamasaura-2020-11-16T13:38:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T14:46:00.000Z",
"author": "Ap7189ap",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/0/0/0",
"6/6/0/5/0/5/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/4",
"6/6/0/5/0/5/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Ap7189ap-2020-11-16T14:46:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Ap7189ap-2020-11-16T14:46:00.000Z-Postcrosser-2020-11-16T14:33:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T15:14:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/0/0/0",
"6/6/0/5/0/6/0/5/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/2",
"6/6/0/5/0/6/0/5/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-16T15:14:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-16T15:14:00.000Z-Ap7189ap-2020-11-16T14:46:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T15:30:00.000Z",
"author": "Agilix",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/6/0/0",
"6/6/0/5/0/6/0/6/0/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/6/0/5",
"6/6/0/5/0/6/0/6/0/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 5,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Agilix-2020-11-16T15:30:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Agilix-2020-11-16T15:30:00.000Z-Postcrosser-2020-11-16T15:14:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T15:50:00.000Z",
"author": "Ap7189ap",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/6/0/9/0/0/0/0",
"6/6/0/5/0/6/0/6/0/9/0/13/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/6/0/9/0/12",
"6/6/0/5/0/6/0/6/0/9/0/13/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 6,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Ap7189ap-2020-11-16T15:50:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Ap7189ap-2020-11-16T15:50:00.000Z-Agilix-2020-11-16T15:30:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T10:09:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/6/0/9/0/14/0/0",
"6/6/0/5/0/6/0/6/0/9/0/14/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"6/6/0/5/0/6/0/6/0/9/0/14/0/1",
"6/6/0/5/0/6/0/6/0/9/0/14/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 7,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-17T10:09:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-17T10:09:00.000Z-Ap7189ap-2020-11-16T15:50:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/0/0",
"7/0/2"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-151.33.155.240-2020-11-16T18:04:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Tunja_voce_della_città_della_Colombia-2020-11-16T18:04:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T18:04:00.000Z",
"author": "151.33.155.240",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/2/0",
"7/2/3/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/2/3/2/3",
"7/2/3/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-151.33.155.240-2020-11-16T18:04:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-151.33.155.240-2020-11-16T18:04:00.000Z-Tunja_voce_della_città_della_Colombia",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T23:36:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/4/0/0",
"7/4/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/4/0/1",
"7/4/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-16T23:36:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-16T23:36:00.000Z-151.33.155.240-2020-11-16T18:04:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T06:39:00.000Z",
"author": "93.36.167.230",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/4/0/5/0/0/0/0",
"7/4/0/5/0/5/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/4/0/5/0/2",
"7/4/0/5/0/5/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-93.36.167.230-2020-11-17T06:39:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-93.36.167.230-2020-11-17T06:39:00.000Z-Postcrosser-2020-11-16T23:36:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T10:08:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/4/0/5/0/6/0/0",
"7/4/0/5/0/6/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"7/4/0/5/0/6/0/1",
"7/4/0/5/0/6/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-17T10:08:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-17T10:08:00.000Z-93.36.167.230-2020-11-17T06:39:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/0/0",
"8/0/2"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-87.14.101.127-2020-11-16T18:12:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Inserire_l'avviso_che_mancano_le_fonti-2020-11-16T18:12:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T18:12:00.000Z",
"author": "87.14.101.127",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/2/0",
"8/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/2/1/2/3",
"8/2/1/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.14.101.127-2020-11-16T18:12:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.14.101.127-2020-11-16T18:12:00.000Z-Inserire_l'avviso_che_mancano_le_fonti",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T07:21:00.000Z",
"author": "Balara86",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/4/0/0",
"8/4/0/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/4/0/5",
"8/4/0/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Balara86-2020-11-17T07:21:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Balara86-2020-11-17T07:21:00.000Z-87.14.101.127-2020-11-16T18:12:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
},
{
"type": "comment",
"timestamp": "2020-11-22T18:11:00.000Z",
"author": "79.31.32.66",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/6/0",
"8/6/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"8/6/1/2/3",
"8/6/1/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-79.31.32.66-2020-11-22T18:11:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-79.31.32.66-2020-11-22T18:11:00.000Z-Inserire_l'avviso_che_mancano_le_fonti",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"9/0/0",
"9/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Pierpao-2020-11-16T18:35:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Server_Mediawiki_-_Segnalazione_incongruenze-2020-11-16T18:35:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-16T18:35:00.000Z",
"author": "Pierpao",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"9/2/0",
"9/2/8/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"9/2/7",
"9/2/8/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Pierpao-2020-11-16T18:35:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Pierpao-2020-11-16T18:35:00.000Z-Server_Mediawiki_-_Segnalazione_incongruenze",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/0/0",
"10/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-5.77.75.205-2020-11-17T08:54:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Avviso_di_Vandalismo-2020-11-17T08:54:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T08:54:00.000Z",
"author": "5.77.75.205",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/2/0",
"10/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/2/3",
"10/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-5.77.75.205-2020-11-17T08:54:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-5.77.75.205-2020-11-17T08:54:00.000Z-Avviso_di_Vandalismo",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T08:57:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/4/0/0",
"10/4/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/4/0/3",
"10/4/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-17T08:57:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-17T08:57:00.000Z-5.77.75.205-2020-11-17T08:54:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T08:59:00.000Z",
"author": "Shivanarayana",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/4/0/5/0/0",
"10/4/0/5/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/4/0/5/0/1",
"10/4/0/5/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Shivanarayana-2020-11-17T08:59:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Shivanarayana-2020-11-17T08:59:00.000Z-ValeJappo-2020-11-17T08:57:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"type": "comment",
"timestamp": "2020-11-20T20:53:00.000Z",
"author": "95.237.218.42",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/6/0",
"10/6/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/6/3",
"10/6/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.237.218.42-2020-11-20T20:53:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.237.218.42-2020-11-20T20:53:00.000Z-Avviso_di_Vandalismo",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
},
{
"type": "comment",
"timestamp": "2020-11-21T10:52:00.000Z",
"author": "95.237.218.42",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/7/0/0",
"10/9/0/7"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"10/9/0/3",
"10/9/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.237.218.42-2020-11-21T10:52:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.237.218.42-2020-11-21T10:52:00.000Z-Avviso_di_Vandalismo",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"11/0/0",
"11/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Enzo_Encius-2020-11-17T11:39:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Richiesta_convalida-2020-11-17T11:39:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T11:39:00.000Z",
"author": "Enzo Encius",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"11/2/0",
"11/10/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"11/10/0/2",
"11/10/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Enzo_Encius-2020-11-17T11:39:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Enzo_Encius-2020-11-17T11:39:00.000Z-Richiesta_convalida",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"12/0/0",
"12/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Pagina_Alberto_Dolfin",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"13/0/0",
"13/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-87.18.165.115-2020-11-17T19:58:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Collaborazione-2020-11-17T19:58:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T19:58:00.000Z",
"author": "87.18.165.115",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"13/2/0",
"13/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"13/2/1/2/3",
"13/2/1/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.18.165.115-2020-11-17T19:58:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.18.165.115-2020-11-17T19:58:00.000Z-Collaborazione",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T22:39:00.000Z",
"author": "87.4.47.34",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"13/4/0/0",
"13/4/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"13/4/0/3",
"13/4/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.4.47.34-2020-11-17T22:39:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.4.47.34-2020-11-17T22:39:00.000Z-87.18.165.115-2020-11-17T19:58:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"14/0/0",
"14/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Sizigia-2020-11-17T22:18:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Procedura_cancellazione-2020-11-17T22:18:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T22:18:00.000Z",
"author": "Sizigia",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"14/2/0",
"14/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"14/2/1",
"14/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Sizigia-2020-11-17T22:18:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Sizigia-2020-11-17T22:18:00.000Z-Procedura_cancellazione",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-17T22:24:00.000Z",
"author": "GryffindorD",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"14/4/0/0/0/0",
"14/4/0/11/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"14/4/0/10",
"14/4/0/11/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-GryffindorD-2020-11-17T22:24:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-GryffindorD-2020-11-17T22:24:00.000Z-Sizigia-2020-11-17T22:18:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"15/0/0",
"15/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Intercontatto-2020-11-18T18:36:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Inserisci_qui_il_titolo_della_richiesta-2020-11-18T18:36:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-18T18:36:00.000Z",
"author": "Intercontatto",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"15/2/0",
"15/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"15/2/1/2/3",
"15/2/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Intercontatto-2020-11-18T18:36:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Intercontatto-2020-11-18T18:36:00.000Z-Inserisci_qui_il_titolo_della_richiesta",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-18T18:39:00.000Z",
"author": "L736E",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"15/4/0/0",
"15/4/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"15/4/0/5",
"15/4/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-L736E-2020-11-18T18:39:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-L736E-2020-11-18T18:39:00.000Z-Intercontatto-2020-11-18T18:36:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/0/0",
"16/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-37.159.55.114-2020-11-19T06:17:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Blocchi_continuativi_sbagliati_e_ingiustificati-2020-11-19T06:17:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T06:17:00.000Z",
"author": "37.159.55.114",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/2/0",
"16/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/2/1",
"16/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-37.159.55.114-2020-11-19T06:17:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-37.159.55.114-2020-11-19T06:17:00.000Z-Blocchi_continuativi_sbagliati_e_ingiustificati",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T06:22:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/0",
"16/4/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/3",
"16/4/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-19T06:22:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-19T06:22:00.000Z-37.159.55.114-2020-11-19T06:17:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T07:31:00.000Z",
"author": "37.159.55.114",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/0",
"16/4/0/5/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/1",
"16/4/0/5/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-37.159.55.114-2020-11-19T07:31:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-37.159.55.114-2020-11-19T07:31:00.000Z-ValeJappo-2020-11-19T06:22:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T07:50:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/0",
"16/4/0/5/0/5/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/1",
"16/4/0/5/0/5/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-19T07:50:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-19T07:50:00.000Z-37.159.55.114-2020-11-19T07:31:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T12:01:00.000Z",
"author": "Daimona Eaytoy",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/0",
"16/4/0/5/0/5/0/3/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/3",
"16/4/0/5/0/5/0/3/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 5,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Daimona_Eaytoy-2020-11-19T12:01:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Daimona_Eaytoy-2020-11-19T12:01:00.000Z-ValeJappo-2020-11-19T07:50:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T12:34:00.000Z",
"author": "87.4.47.34",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/0",
"16/4/0/5/0/5/0/3/0/7/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/1",
"16/4/0/5/0/5/0/3/0/7/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 6,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.4.47.34-2020-11-19T12:34:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.4.47.34-2020-11-19T12:34:00.000Z-Daimona_Eaytoy-2020-11-19T12:01:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T12:45:00.000Z",
"author": "Daimona Eaytoy",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/0",
"16/4/0/5/0/5/0/3/0/7/0/5/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/1",
"16/4/0/5/0/5/0/3/0/7/0/5/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 7,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Daimona_Eaytoy-2020-11-19T12:45:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Daimona_Eaytoy-2020-11-19T12:45:00.000Z-87.4.47.34-2020-11-19T12:34:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T13:08:00.000Z",
"author": "87.4.47.34",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/0",
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/3",
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 8,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-87.4.47.34-2020-11-19T13:08:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-87.4.47.34-2020-11-19T13:08:00.000Z-Daimona_Eaytoy-2020-11-19T12:45:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T13:15:00.000Z",
"author": "Daimona Eaytoy",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/0",
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/1",
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 9,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Daimona_Eaytoy-2020-11-19T13:15:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Daimona_Eaytoy-2020-11-19T13:15:00.000Z-87.4.47.34-2020-11-19T13:08:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T18:42:00.000Z",
"author": "L736E",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/5/0/0",
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/5/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/5/0/1",
"16/4/0/5/0/5/0/3/0/7/0/5/0/5/0/7/0/5/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 10,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-L736E-2020-11-19T18:42:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-L736E-2020-11-19T18:42:00.000Z-Daimona_Eaytoy-2020-11-19T13:15:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
}
]
}
]
}
]
}
]
},
{
"type": "comment",
"timestamp": "2020-11-19T19:31:00.000Z",
"author": "151.47.37.37",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/6/0/0",
"16/6/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/6/0/1",
"16/6/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-151.47.37.37-2020-11-19T19:31:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-151.47.37.37-2020-11-19T19:31:00.000Z-37.159.55.114-2020-11-19T06:17:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T21:10:00.000Z",
"author": "Popop",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/6/0/5/0/0",
"16/6/0/5/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"16/6/0/5/0/3",
"16/6/0/5/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Popop-2020-11-19T21:10:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Popop-2020-11-19T21:10:00.000Z-151.47.37.37-2020-11-19T19:31:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"17/0/0",
"17/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Postcrosser-2020-11-19T10:13:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Aiuto_creazione_pagina_biografia-2020-11-19T10:13:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T10:13:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"17/2/0",
"17/6/8/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"17/6/8/1",
"17/6/8/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-19T10:13:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-19T10:13:00.000Z-Aiuto_creazione_pagina_biografia",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"18/0/0",
"18/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-LuiDeLu-2020-11-19T13:21:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Brigataes-2020-11-19T13:21:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T13:21:00.000Z",
"author": "LuiDeLu",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"18/2/0",
"18/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"18/2/3",
"18/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-LuiDeLu-2020-11-19T13:21:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-LuiDeLu-2020-11-19T13:21:00.000Z-Brigataes",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T14:48:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"18/4/0/0",
"18/4/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"18/4/0/1",
"18/4/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-19T14:48:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-19T14:48:00.000Z-LuiDeLu-2020-11-19T13:21:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/0/0",
"19/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Scalorbio-2020-11-19T17:11:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Ricerca_vecchie_discussione_nel_Bar-2020-11-19T17:11:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T17:11:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/2/0",
"19/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/2/1",
"19/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T17:11:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T17:11:00.000Z-Ricerca_vecchie_discussione_nel_Bar",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T17:18:00.000Z",
"author": "GryffindorD",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/0/0/0",
"19/4/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/6",
"19/4/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-GryffindorD-2020-11-19T17:18:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-GryffindorD-2020-11-19T17:18:00.000Z-Scalorbio-2020-11-19T17:11:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T17:31:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/8/0/0/0/0",
"19/4/0/8/0/7/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/8/0/4",
"19/4/0/8/0/7/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T17:31:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T17:31:00.000Z-GryffindorD-2020-11-19T17:18:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T17:36:00.000Z",
"author": "GryffindorD",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/8/0/8/0/0/0/0",
"19/4/0/8/0/8/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/8/0/8/0/6",
"19/4/0/8/0/8/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-GryffindorD-2020-11-19T17:36:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-GryffindorD-2020-11-19T17:36:00.000Z-Scalorbio-2020-11-19T17:31:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T17:39:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/8/0/8/0/8/0/0",
"19/4/0/8/0/8/0/8/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"19/4/0/8/0/8/0/8/0/3",
"19/4/0/8/0/8/0/8/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 5,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T17:39:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T17:39:00.000Z-GryffindorD-2020-11-19T17:36:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/0/0",
"20/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Scalorbio-2020-11-19T18:09:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Rinomina_disambigua_ecc.-2020-11-19T18:09:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T18:09:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/2/0",
"20/2/12/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/2/9",
"20/2/12/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T18:09:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T18:09:00.000Z-Rinomina_disambigua_ecc.",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T18:23:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/0",
"20/4/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/3",
"20/4/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T18:23:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T18:23:00.000Z-Scalorbio-2020-11-19T18:09:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T18:27:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/7/0/0",
"20/4/0/7/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/7/0/3",
"20/4/0/7/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T18:27:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T18:27:00.000Z-Scalorbio-2020-11-19T18:23:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T18:28:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/7/0/7/0/0/0/0",
"20/4/0/7/0/7/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/7/0/7/0/2",
"20/4/0/7/0/7/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-19T18:28:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-19T18:28:00.000Z-Scalorbio-2020-11-19T18:27:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T18:30:00.000Z",
"author": "Scalorbio",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/7/0/7/0/4/0/0",
"20/4/0/7/0/7/0/4/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"20/4/0/7/0/7/0/4/0/3",
"20/4/0/7/0/7/0/4/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 5,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Scalorbio-2020-11-19T18:30:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Scalorbio-2020-11-19T18:30:00.000Z-ValeJappo-2020-11-19T18:28:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"21/0/0",
"21/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Vale93b-2020-11-19T20:38:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Paolo_Boninsegna-2020-11-19T20:38:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T20:38:00.000Z",
"author": "Vale93b",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"21/2/0",
"21/4/0/10/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"21/4/0/7",
"21/4/0/10/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Vale93b-2020-11-19T20:38:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Vale93b-2020-11-19T20:38:00.000Z-Paolo_Boninsegna",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"22/0/0",
"22/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Janik98-2020-11-19T20:51:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Archivio_discussione_utente-2020-11-19T20:51:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T20:51:00.000Z",
"author": "Janik98",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"22/2/0",
"22/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"22/2/1",
"22/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Janik98-2020-11-19T20:51:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Janik98-2020-11-19T20:51:00.000Z-Archivio_discussione_utente",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-19T20:54:00.000Z",
"author": "Civvì",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"22/4/0/0/0/0",
"22/4/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"22/4/0/2",
"22/4/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Civvì-2020-11-19T20:54:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Civvì-2020-11-19T20:54:00.000Z-Janik98-2020-11-19T20:51:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/0/0",
"23/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Syphax98-2020-11-20T11:09:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Commenti_inutili_sulle_pagine_di_discussione-2020-11-20T11:09:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T11:09:00.000Z",
"author": "Syphax98",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/2/0",
"23/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/2/3",
"23/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Syphax98-2020-11-20T11:09:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Syphax98-2020-11-20T11:09:00.000Z-Commenti_inutili_sulle_pagine_di_discussione",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T11:18:00.000Z",
"author": "Agilix",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/0/0/0",
"23/4/0/11/78"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/8",
"23/4/0/11/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Agilix-2020-11-20T11:18:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Agilix-2020-11-20T11:18:00.000Z-Syphax98-2020-11-20T11:09:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T11:20:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/0/0/0",
"23/4/0/12/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/6",
"23/4/0/12/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-20T11:20:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-20T11:20:00.000Z-Agilix-2020-11-20T11:18:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T11:35:00.000Z",
"author": "Syphax98",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/0/0/0",
"23/4/0/12/0/8/0/11/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/8",
"23/4/0/12/0/8/0/11/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Syphax98-2020-11-20T11:35:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Syphax98-2020-11-20T11:35:00.000Z-ValeJappo-2020-11-20T11:20:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T11:46:00.000Z",
"author": "Agilix",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/0/0/0",
"23/4/0/12/0/8/0/12/0/23/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/20",
"23/4/0/12/0/8/0/12/0/23/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 5,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Agilix-2020-11-20T11:46:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Agilix-2020-11-20T11:46:00.000Z-Syphax98-2020-11-20T11:35:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T11:57:00.000Z",
"author": "Idraulico liquido",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/24/0/0",
"23/4/0/12/0/8/0/12/0/24/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/24/0/1",
"23/4/0/12/0/8/0/12/0/24/0/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 6,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Idraulico_liquido-2020-11-20T11:57:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Idraulico_liquido-2020-11-20T11:57:00.000Z-Agilix-2020-11-20T11:46:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T12:14:00.000Z",
"author": "Pierpao",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/0/0",
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/0/8/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/0/7",
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/0/8/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 8,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Pierpao-2020-11-20T12:14:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Pierpao-2020-11-20T12:14:00.000Z-Idraulico_liquido-2020-11-20T11:57:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment skips indentation level"
],
"replies": []
},
{
"type": "comment",
"timestamp": "2020-11-20T12:16:00.000Z",
"author": "Pierpao",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/2/0",
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/2/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/2/1",
"23/4/0/12/0/8/0/12/0/24/0/5/0/0/2/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 8,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Pierpao-2020-11-20T12:16:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Pierpao-2020-11-20T12:16:00.000Z-Idraulico_liquido-2020-11-20T11:57:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
}
]
}
]
},
{
"type": "comment",
"timestamp": "2020-11-20T12:18:00.000Z",
"author": "Syphax98",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/6/0/0/0",
"23/6/5/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/6/2",
"23/6/5/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Syphax98-2020-11-20T12:18:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Syphax98-2020-11-20T12:18:00.000Z-Commenti_inutili_sulle_pagine_di_discussione",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T12:45:00.000Z",
"author": "Pierpao",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/1",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 9,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Pierpao-2020-11-20T12:45:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Pierpao-2020-11-20T12:45:00.000Z-Syphax98-2020-11-20T12:18:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment skips indentation level"
],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T17:24:00.000Z",
"author": "95.237.218.42",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/0",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/3",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 10,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.237.218.42-2020-11-20T17:24:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.237.218.42-2020-11-20T17:24:00.000Z-Pierpao-2020-11-20T12:45:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T20:49:00.000Z",
"author": "95.237.218.42",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/0",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/1",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 11,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.237.218.42-2020-11-20T20:49:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.237.218.42-2020-11-20T20:49:00.000Z-95.237.218.42-2020-11-20T17:24:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T20:56:00.000Z",
"author": "Enzo Encius",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/5/0/0/0/0",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/5/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/5/0/2",
"23/8/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/3/0/7/0/5/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 12,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Enzo_Encius-2020-11-20T20:56:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Enzo_Encius-2020-11-20T20:56:00.000Z-95.237.218.42-2020-11-20T20:49:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"24/0/0",
"24/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Wim_b-2020-11-20T21:55:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-maometto-2020-11-20T21:55:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T21:55:00.000Z",
"author": "Wim b",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"24/2/0",
"24/12/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"24/12/0/1",
"24/12/0/2/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Wim_b-2020-11-20T21:55:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Wim_b-2020-11-20T21:55:00.000Z-maometto",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-20T22:19:00.000Z",
"author": "Lepido",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"24/12/0/3/0/0",
"24/12/0/3/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"24/12/0/3/0/3",
"24/12/0/3/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Lepido-2020-11-20T22:19:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Lepido-2020-11-20T22:19:00.000Z-Wim_b-2020-11-20T21:55:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment skips indentation level"
],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"25/0/0",
"25/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-ValeJappo-2020-11-21T15:51:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Problema_preferenze-2020-11-21T15:51:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-21T15:51:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"25/2/0/0",
"25/2/6/5"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"25/2/6/3",
"25/2/6/4/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-21T15:51:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-21T15:51:00.000Z-Problema_preferenze",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/0/0",
"26/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Sheen_Hossain-2020-11-21T17:53:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Daydreamer-2020-11-21T17:53:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-21T17:53:00.000Z",
"author": "Sheen Hossain",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/2/0",
"26/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/2/1/2/3",
"26/2/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Sheen_Hossain-2020-11-21T17:53:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Sheen_Hossain-2020-11-21T17:53:00.000Z-Daydreamer",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-21T17:56:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/4/0/0/0/0",
"26/4/0/5/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/4/0/4",
"26/4/0/5/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-21T17:56:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-21T17:56:00.000Z-Sheen_Hossain-2020-11-21T17:53:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-21T19:28:00.000Z",
"author": "95.237.218.42",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/4/0/6/0/0/0/0",
"26/4/0/6/0/9/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"26/4/0/6/0/6",
"26/4/0/6/0/9/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.237.218.42-2020-11-21T19:28:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.237.218.42-2020-11-21T19:28:00.000Z-ValeJappo-2020-11-21T17:56:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/0/0",
"27/0/2"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Lucchinifederico-2020-11-21T23:02:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Come_inserire_\"pilota_automobilistico_italiano\"_sotto_il_nome?_(nella_versione_m-2020-11-21T23:02:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-21T23:02:00.000Z",
"author": "Lucchinifederico",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/2/0",
"27/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/2/3",
"27/2/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Lucchinifederico-2020-11-21T23:02:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Lucchinifederico-2020-11-21T23:02:00.000Z-Come_inserire_\"pilota_automobilistico_italiano\"_sotto_il_nome?_(nella_versione_m",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-22T00:06:00.000Z",
"author": "Postcrosser",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/4/0/0",
"27/4/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/4/0/1",
"27/4/0/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Postcrosser-2020-11-22T00:06:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Postcrosser-2020-11-22T00:06:00.000Z-Lucchinifederico-2020-11-21T23:02:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-22T00:16:00.000Z",
"author": "Ap7189ap",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/4/0/5/0/0",
"27/4/0/5/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"27/4/0/5/0/5",
"27/4/0/5/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Ap7189ap-2020-11-22T00:16:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Ap7189ap-2020-11-22T00:16:00.000Z-Postcrosser-2020-11-22T00:06:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"28/0/0",
"28/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Vale93b-2020-11-22T10:24:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Inserimento_di_un_nuovo_formato_di_pasta_fresca_che_contraddistingue_un_luogo_sp-2020-11-22T10:24:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-22T10:24:00.000Z",
"author": "Vale93b",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"28/2/0",
"28/6/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"28/6/0/3",
"28/6/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Vale93b-2020-11-22T10:24:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Vale93b-2020-11-22T10:24:00.000Z-Inserimento_di_un_nuovo_formato_di_pasta_fresca_che_contraddistingue_un_luogo_sp",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"29/0/0",
"29/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Pierpao-2020-11-22T10:46:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Inserimento_di_un_nuovo_formato_di_pasta_fresca_che_contraddistingue_un_luogo_sp-2020-11-22T10:46:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-22T10:46:00.000Z",
"author": "Pierpao",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"29/2/0",
"29/6/0/12/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"29/6/0/11",
"29/6/0/12/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Pierpao-2020-11-22T10:46:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Pierpao-2020-11-22T10:46:00.000Z-Inserimento_di_un_nuovo_formato_di_pasta_fresca_che_contraddistingue_un_luogo_sp",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [
"Comment starts and ends with different indentation"
],
"replies": []
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/0/0",
"30/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Istheendoftheworldasweknowit-2020-11-23T08:37:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Aiuto_sugli_schemi-2020-11-23T08:37:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T08:37:00.000Z",
"author": "Istheendoftheworldasweknowit",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/2/0",
"30/2/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/2/1/2/3",
"30/2/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Istheendoftheworldasweknowit-2020-11-23T08:37:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Istheendoftheworldasweknowit-2020-11-23T08:37:00.000Z-Aiuto_sugli_schemi",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T08:43:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/4/0/0/0/0",
"30/4/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/4/0/2",
"30/4/0/3/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-23T08:43:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-23T08:43:00.000Z-Istheendoftheworldasweknowit-2020-11-23T08:37:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T08:45:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/4/0/4/0/0/0/0",
"30/4/0/4/0/11/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/4/0/4/0/10",
"30/4/0/4/0/11/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-23T08:45:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-23T08:45:00.000Z-ValeJappo-2020-11-23T08:43:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T11:50:00.000Z",
"author": "95.244.17.210",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/4/0/4/0/12/0/0",
"30/4/0/4/0/12/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"30/4/0/4/0/12/0/3",
"30/4/0/4/0/12/0/6/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.244.17.210-2020-11-23T11:50:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.244.17.210-2020-11-23T11:50:00.000Z-ValeJappo-2020-11-23T08:45:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"31/0/0",
"31/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Pinkgirlinside-2020-11-23T09:16:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-info-2020-11-23T09:16:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T09:16:00.000Z",
"author": "Pinkgirlinside",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"31/2/0",
"31/4/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"31/4/1/2/3",
"31/4/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Pinkgirlinside-2020-11-23T09:16:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Pinkgirlinside-2020-11-23T09:16:00.000Z-info",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T10:21:00.000Z",
"author": "Lepido",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"31/6/0/0",
"31/6/4/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"31/6/4/1",
"31/6/4/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Lepido-2020-11-23T10:21:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Lepido-2020-11-23T10:21:00.000Z-Pinkgirlinside-2020-11-23T09:16:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/0/0",
"32/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Patrizia_Giancotti-2020-11-23T09:58:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-copia_delle_modifiche-2020-11-23T09:58:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T09:58:00.000Z",
"author": "Patrizia Giancotti",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/2/0",
"32/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/2/1",
"32/2/4/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Patrizia_Giancotti-2020-11-23T09:58:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Patrizia_Giancotti-2020-11-23T09:58:00.000Z-copia_delle_modifiche",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T10:01:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/4/0/0/0/0",
"32/4/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/4/0/6",
"32/4/0/7/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-23T10:01:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-23T10:01:00.000Z-Patrizia_Giancotti-2020-11-23T09:58:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T10:08:00.000Z",
"author": "Lepido",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/4/0/8/0/0",
"32/4/0/8/0/10/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/4/0/8/0/7",
"32/4/0/8/0/10/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 3,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Lepido-2020-11-23T10:08:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Lepido-2020-11-23T10:08:00.000Z-ValeJappo-2020-11-23T10:01:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T10:53:00.000Z",
"author": "Etienne",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/4/0/8/0/11/0/0/0/0",
"32/4/0/8/0/11/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"32/4/0/8/0/11/0/4",
"32/4/0/8/0/11/0/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 4,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Etienne-2020-11-23T10:53:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Etienne-2020-11-23T10:53:00.000Z-Lepido-2020-11-23T10:08:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
]
}
]
},
{
"placeholderHeading": false,
"type": "heading",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/0/0",
"33/0/1"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"headingLevel": 2,
"level": 0,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "h-Ferdinando_Fedi-2020-11-23T11:55:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "h-Inserimento_voce_su_Wikipedia-2020-11-23T11:55:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T11:55:00.000Z",
"author": "Ferdinando Fedi",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/2/2",
"33/8/1/4"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/8/1/2/3",
"33/8/1/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 1,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-Ferdinando_Fedi-2020-11-23T11:55:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-Ferdinando_Fedi-2020-11-23T11:55:00.000Z-Inserimento_voce_su_Wikipedia",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": [
{
"type": "comment",
"timestamp": "2020-11-23T12:00:00.000Z",
"author": "95.244.17.210",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/10/0/0/0/0",
"33/10/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/10/2/5",
"33/10/2/8/26"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-95.244.17.210-2020-11-23T12:00:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-95.244.17.210-2020-11-23T12:00:00.000Z-Ferdinando_Fedi-2020-11-23T11:55:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
},
{
"type": "comment",
"timestamp": "2020-11-23T12:08:00.000Z",
"author": "ValeJappo",
"range": [
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/10/4/0",
"33/10/4/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
],
"signatureRanges": [
[
tests: Fix root node / container handling Since times immemorial, and for reasons lost to history, our test code was adding an extra <div> wrapper before parsing the HTML used for tests. This wasn't a problem, until now, because I want to add some tests for T303396 that need to check that the *real* wrappers present in some test cases are handled correctly. Changes to test cases mostly remove a leading "0/" from serialized ranges, corresponding to removing the extra wrapper. Change-Id: Ia50e3590538c8cd274b02d2a937ba1a3fbb4ac89
2022-03-09 19:32:51 +00:00
"33/10/4/5",
"33/10/4/6/25"
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
]
],
"level": 2,
Introduce comment "names" to identify comments across revisions/pages The existing comment IDs can't be used to find the same comment on a different revision or page (when it's transcluded), because they depend on the comment's parent and its position on the page. Comment names depend only on the author and timestamp. The trade-off is that they can't distinguish comments posted within the same minute, or in the same edit, so we will still need the IDs sometimes. Prefer using comment names when replying, if they're not ambiguous. This fixes T273413 and T275821. Heading names depend on the author and timestamp of the oldest comment. This way we don't have to detect changes to the heading text, but we can't distinguish headings without any comments. Bug: T274685 Bug: T273413 Bug: T275821 Change-Id: Id85c50ba38d1e532cec106708c077b908a3fcd49
2021-02-12 19:16:13 +00:00
"name": "c-ValeJappo-2020-11-23T12:08:00.000Z",
Make IDs (to be used as URL hashes) wikitext safe * Use hyphens instead of pipes a separators * Use underscores for spaces in usernames Change-Id: I6efd9739fc73e45002e50e64c43ce0de1c2f1239
2021-03-17 14:39:41 +00:00
"id": "c-ValeJappo-2020-11-23T12:08:00.000Z-Ferdinando_Fedi-2020-11-23T11:55:00.000Z",
Use tabs for indentation in JSON test files Change-Id: I1d8f8b33b19bcff249ad08dfe687f87f5e5bf9bf
2021-01-26 23:55:15 +00:00
"warnings": [],
"replies": []
}
]
}
]
}
Add tests covering it.wp unsigned comment template Bug: T268178 Bug: T268589 Change-Id: Icd353275b3b8191eddbff4d72984a8c2c8e6cdd6
2020-11-25 00:06:56 +00:00
]
Reference in a new issue Copy permalink