Markdown Headings are valid with or without a space after the # about publickb

[nathanyoung]

cc: @dmak78 @thenickcox

@mattfordham is on vacation.

[osbornm]

Who approved that!?

[thenickcox]

Just wanted to get back to you quickly on this. We're using a third party markdown parsing library that doesn't, at first glance, allow configuration of making affordances for things like that. We can research early next week if there are other options, but for now, unfortunately, we don't have any control over the markdown parsing.

[thenickcox]

Bump @osbornm cc @nathanyoung. Just didn't want this to slip through the cracks.

[nathanyoung]

Is it possible for the commit analyzer to check to make sure headers have a trailing space?

[osbornm]

Yes but the real problem is that it's valid markdown and many markdown editors make headings that way.

Cheers,
Matthew M. Osborn

On Aug 26, 2015, at 11:13, Nathan Young <[email protected]mailto:[email protected]> wrote:

Is it possible for the commit analyzer to check to make sure headers have a trailing space?

Reply to this email directly or view it on GitHubhttps://github.com//issues/319#issuecomment-135127835.

[keithresar]

FWIW at one point our parser was leading space agnostic - I swear this rendered fine in my pages:

###Heading

I discovered this changed at some point and needed to update all the KBs that were missing that space.