markdownlint/test/fenced-code-in-list.md

# Heading

- Item

  ```javascript
  debugger;


  debugger;
  ```

  text

- Item

  - Subitem

    ```javascript
    debugger;


    debugger;
    ```

    text

  - Subitem

- Item

  - Subitem

    ```javascript
    debugger; debugger; debugger; debugger; debugger; debugger; debugger; debugger; debugger; debugger;
    ```

<!-- markdownlint-configure-file {
  "line-length": {
    "code_blocks": false
  }
} -->
Use tokens (vs. RegExp) for identifying fenced code blocks (fixes #151, fixes #152, fixes #155). 2019-01-10 21:29:27 -08:00			`# Heading`

			`- Item`

			```javascript
			`debugger;`


			`debugger;`
			```

			`text`

			`- Item`

			`- Subitem`

			```javascript
			`debugger;`


			`debugger;`
			```

			`text`

			`- Subitem`

			`- Item`

			`- Subitem`

			```javascript
			`debugger; debugger; debugger; debugger; debugger; debugger; debugger; debugger; debugger; debugger;`
			```
Simplify test directory by moving all JSON configuration for scenario tests into the Markdown file via markdownlint-configure-file. 2023-03-15 21:26:22 -07:00
			`<!-- markdownlint-configure-file {`
Always refer to rules by name (not number) in test configuration. 2023-07-28 14:33:03 +10:00			`"line-length": {`
Simplify test directory by moving all JSON configuration for scenario tests into the Markdown file via markdownlint-configure-file. 2023-03-15 21:26:22 -07:00			`"code_blocks": false`
			`}`
			`} -->`