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
Markdown linting rule MD030, which determines the number of spaces after a list marker, suggests 1 space by default. Validation of markdown on our GitHub setup suggests 2 and so generates listing warnings with a default formatted document.
MD030/list-marker-space Spaces after list markers [Expected: 2; Actual: 1]
Is there any reason why we shouldn't use the default of 1?
The text was updated successfully, but these errors were encountered:
We use one space for unordered lists, so that blocks in list items were padded by two spaces.
- Hello
Two leading spaces here 👍
``` code listing```- World
If we do the same for the ordered lists, these elements (including code listings) will be padded by three spaces.
1. Hello
Three leading spaces here 👎
``` code listing```1. World
Adding one extra space makes this offset even, which simplifies actions like select + tab / select + shift tab in the editor.
1. Hello
Four leading spaces here 👍
``` code listing```1. World
Because we don't know in advance which lists will have blocks and which ones will remain simple, the same rule applies everywhere. Happy to update our setup if there is possibility for some other convenient configuration.
Markdown linting rule MD030, which determines the number of spaces after a list marker, suggests 1 space by default. Validation of markdown on our GitHub setup suggests 2 and so generates listing warnings with a default formatted document.
MD030/list-marker-space Spaces after list markers [Expected: 2; Actual: 1]
Is there any reason why we shouldn't use the default of 1?
The text was updated successfully, but these errors were encountered: