kylef
commented
5 years ago @klokane I believe you get two separate warnings in that case, it is two separate cases of incorrectly indented blocks, this is the same as before.
Now:
warning: (10) message-body asset is expected to be a pre-formatted code block, every of its line indented by exactly 8 spaces or 2 tabs :48:232
warning: (10) message-body asset is expected to be a pre-formatted code block, every of its line indented by exactly 8 spaces or 2 tabs :237:318Master:
warning: (10) message-body asset is expected to be a pre-formatted code block, every of its line indented by exactly 8 spaces or 2 tabs :48:13;65:13;82:13;99:13;116:13;133:13;150:13;167:13;184:13;201:13;218:14
warning: (10) message-body asset is expected to be a pre-formatted code block, every of its line indented by exactly 8 spaces or 2 tabs :237:13;254:13;271:13;288:13;305:13
Otherwise we end up creating a separate source map entry for each line excluding part of the indentation which for large invalid indented blocks causes memory problems in multiple parts of the stack (Drafter, Minim and also in editor integrations and validators). This has decent impact on parse time.
From a real-world API Description document I came across:
Before:
This is very truncated because I cannot use it in GitHub:
Use side-scroll
After
With Line Numbers: