Single-column tables rendered incorrectly in README.md

[ichordev]

GitHub's markdown allows for single-column tables.

My Header
Item A
Item B
Item C

Written as:

| My Header |
|-----------|
| Item A    |
| Item B    |
| Item C    |

However on the DUB registry in the Info section of a package, they turn into this soup:

| My Header | |-----------| | Item A | | Item B | | Item C |

You can see this happen with a few BindBC packages on the registry.

• https://code.dlang.org/packages/bindbc-sdl
• https://code.dlang.org/packages/bindbc-bgfx
• https://code.dlang.org/packages/bindbc-opus

It's a small thing, but it makes the structure of a document look much nicer when they're rendered properly. They're even used in the DIP template.

[WebFreak001]

we might want to consider using https://github.com/AuburnSounds/commonmark-d instead of the vibe built-in markdown capabilities (and maybe even deprecate/separate them from vibe)

[ichordev]

we might want to consider using https://github.com/AuburnSounds/commonmark-d

Ooh, would that mean that HTML tags would get rendered properly, too?

[WebFreak001]

the security aspect is something we would need to test for, since we don't want to accept any script tags or any kind of script injection

[ichordev]

Wow… why does that markdown standard allow you to use <script>!? HTML in markdown is usually just meant to be for advanced formatting (images, spoilers, etc.)

[WebFreak001]

well since the markdown converter might just pipe HTML tags as-is to the output. I don't see any allow-list of tags in that parser, so it might not be in the scope of it.

[ichordev]

Well the spec it follows says it should output “raw, unescaped HTML”, so I’m thinking the parser does that to be compliant.