You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* List entry
<!-- eslint-disable strict -->
```js
console.log('a');
```
* List entry
<!-- eslint-skip -->
```js
> console.log('a');
```
No errors.
Test doc 2:
* List entry
<!-- eslint-disable strict -->
```js
console.log('a');
```
* List entry
<!-- eslint-skip -->
```js
> console.log('a');
```
Comments are ignored:
4:1 error Use the global form of 'use strict' strict 10:1 error Parsing error: Unexpected token >
No other block or span Markdown elements have this issue. All list elements (unordered with * + - or ordered with 1. ...) have the same issue (both one- and multiline).
The text was updated successfully, but these errors were encountered:
vsemozhetbyt
changed the title
List entry without followed empty line eliminate configuration/skip comments
List entry without followed empty line eliminates configuration/skip comments
Jul 4, 2017
Comment attachment was sensitive to whitespace around the code block and
preceding comments. In some cases, the parser would place comments as
descendants of code blocks' preceding sibling nodes. However, a
depth-first traversal of the tree will still encounter the comments in
linear order, which is sufficient for our purposes.
Comment attachment was sensitive to whitespace around the code block and
preceding comments. In some cases, the parser would place comments as
descendants of code blocks' preceding sibling nodes. However, a
depth-first traversal of the tree will still encounter the comments in
linear order, which is sufficient for our purposes.
[email protected]
,[email protected]
Test doc 1:
No errors.
Test doc 2:
Comments are ignored:
No other block or span Markdown elements have this issue. All list elements (unordered with
* + -
or ordered with1. ...
) have the same issue (both one- and multiline).The text was updated successfully, but these errors were encountered: