Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed the header rendering to match that of GFM #110

Merged
merged 1 commit into from
Nov 26, 2017
Merged

Fixed the header rendering to match that of GFM #110

merged 1 commit into from
Nov 26, 2017

Conversation

vwal
Copy link
Contributor

@vwal vwal commented Nov 21, 2017

Removed an extraneous ? from the header regex. GFM does not render headers if there's no space between the hash(es) and the text. In other words:

#header

is rendered as:

#header

Whereas:

# header

is rendered as:

header

With this change vmd complies with the GFM also in this regard.

@@ -116,7 +116,7 @@ function gemojiToImages() {
}

function fixHeadings() {
Copy link
Collaborator

@maxkueng maxkueng Nov 21, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the whole fixHeadings handler can be removed. It looks like all it does did is make it possible to create headings without spaces after the #.

@maxkueng
Copy link
Collaborator

Cool! It appears that GitHub changed how it renders the headings. In issue #90 we actually added support for headings without spaces after the hashes because GitHub supported it even though it wasn't totally correct markdown.

I added a comment. Maybe you can take a look at it.

@maxkueng maxkueng merged commit 4fdedbf into yoshuawuyts:master Nov 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants