mediawiki-extensions-Discus.../tests/cases/no-heading/no-heading.json

[
  {
    "placeholderHeading": true,
    "type": "heading",
    "range": [
      "0",
      "0"
    ],
    "headingLevel": 99,
    "level": 0,
    "id": "h||2020-01-22T23:19:00.000Z",
    "warnings": [],
    "replies": [
      {
        "type": "comment",
        "timestamp": "2020-01-22T23:19:00.000Z",
        "author": "Matma Rex",
        "range": [
          "0/1/0",
          "0/1/2/29"
        ],
        "signatureRanges": [
          [
            "0/1/1",
            "0/1/2/29"
          ]
        ],
        "level": 1,
        "id": "c|Matma Rex|2020-01-22T23:19:00.000Z",
        "warnings": [],
        "replies": []
      }
    ]
  }
]
Handle comments before first section heading The loop in parser.js assumed that there was always a heading before any comments (not counting the page title, only section headings). Bug: T243869 Change-Id: I3a0bb06716e75d4a17e25c40748673a071ee5f30 2020-01-28 23:35:26 +00:00			`[`
			`{`
Fix edit summary for comments in 0th section (no heading) Bug: T245765 Change-Id: I9eb4726ef096b8d7459cc1409814514ec1dc89ae 2020-02-20 20:24:07 +00:00			`"placeholderHeading": true,`
Handle comments before first section heading The loop in parser.js assumed that there was always a heading before any comments (not counting the page title, only section headings). Bug: T243869 Change-Id: I3a0bb06716e75d4a17e25c40748673a071ee5f30 2020-01-28 23:35:26 +00:00			`"type": "heading",`
			`"range": [`
			`"0",`
			`"0"`
			`],`
Connect sub-threads to their parent threads Our threads now also contain all replies to their sub-threads. This is similar to how sections work in MediaWiki, where the parent section also contains the content of all the lower-level sections. We're going to need this for notifications about replies in a thread. Bug: T264478 Change-Id: I241fc58e2088a7555942824b0f184ed21e3a8b6f 2020-10-01 19:36:11 +00:00			`"headingLevel": 99,`
Handle comments before first section heading The loop in parser.js assumed that there was always a heading before any comments (not counting the page title, only section headings). Bug: T243869 Change-Id: I3a0bb06716e75d4a17e25c40748673a071ee5f30 2020-01-28 23:35:26 +00:00			`"level": 0,`
Add oldest timestamp in the thread to heading IDs To avoid old threads re-appearing on popular pages when someone uses a vague title (e.g. dozens of threads titled "question" on [[Wikipedia:Help desk]]: https://w.wiki/fbN), include the oldest timestamp in the thread (i.e. date the thread was started) in the heading ID. Bug: T264478 Change-Id: If918bfd5e025248923d1939bc86916697ead95a0 2020-10-07 15:48:20 +00:00			`"id": "h\|\|2020-01-22T23:19:00.000Z",`
Move warnings stuff from CommentItem to ThreadItem After recent changes allowing ThreadItems to have IDs, they can now also have warnings about duplicate IDs. Bug: T267035 Change-Id: If3edfe34e6e29741e29fac8946a3c88badc4ab7f 2020-11-02 18:35:38 +00:00			`"warnings": [],`
Handle comments before first section heading The loop in parser.js assumed that there was always a heading before any comments (not counting the page title, only section headings). Bug: T243869 Change-Id: I3a0bb06716e75d4a17e25c40748673a071ee5f30 2020-01-28 23:35:26 +00:00			`"replies": [`
			`{`
			`"type": "comment",`
			`"timestamp": "2020-01-22T23:19:00.000Z",`
			`"author": "Matma Rex",`
			`"range": [`
			`"0/1/0",`
			`"0/1/2/29"`
			`],`
parser: Return signature and timestamp ranges Currently not used for anything. May be used later for editing comments (T245225) or reformatting timestamps (T240360). Note that a comment may have multiple signatures+timestamps, and we return them all so that you have to deal with that. Fix some unrelated incorrect documentation comments. Bug: T245220 Change-Id: I51b8bf4a3bb7968f35e32c7e44c95c2ab079d9ac 2020-03-04 16:14:47 +00:00			`"signatureRanges": [`
			`[`
			`"0/1/1",`
			`"0/1/2/29"`
			`]`
			`],`
Handle comments before first section heading The loop in parser.js assumed that there was always a heading before any comments (not counting the page title, only section headings). Bug: T243869 Change-Id: I3a0bb06716e75d4a17e25c40748673a071ee5f30 2020-01-28 23:35:26 +00:00			`"level": 1,`
Disambiguate comments by parent ID, rather than sequential numbers Sequential numbers aren't great because they change when an earlier comment is archived. Parent comment/heading IDs should change less often. This also makes much more sense for disambiguating subsections, e.g. a dozen identical ===Votes=== sections for a dozen proposals. Bug: T264478 Change-Id: I466454984fd919ebef35f2b37ddb5d86dc842996 2020-10-01 20:13:47 +00:00			`"id": "c\|Matma Rex\|2020-01-22T23:19:00.000Z",`
Fix some TODOs about test data We avoided fixing these because it causes changes in just about all of the test data, which is annoying when reviewing or blaming changes. But the previous several commits also caused changes in just about all of the test data, so we might as well do this too. Change-Id: I83b64d83b6f12c04dc06c0cadff7cdd89417e137 2020-10-07 14:45:19 +00:00			`"warnings": [],`
Handle comments before first section heading The loop in parser.js assumed that there was always a heading before any comments (not counting the page title, only section headings). Bug: T243869 Change-Id: I3a0bb06716e75d4a17e25c40748673a071ee5f30 2020-01-28 23:35:26 +00:00			`"replies": []`
			`}`
			`]`
			`}`
			`]`