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

Use kramdown GFM parser #1436

Merged
merged 1 commit into from
Jan 20, 2025
Merged

Use kramdown GFM parser #1436

merged 1 commit into from
Jan 20, 2025

Conversation

deivid-rodriguez
Copy link
Member

What was the end-user problem that led to this PR?

The problem was that some markdown pages are not rendered correctly,

What was your diagnosis of the problem?

We're using options that are exclusive to that parser, so we should explicitly force it.

What is your fix for the problem, implemented in this PR?

My fix is to explicit set the parser that we want.

Before:

Captura de pantalla 2025-01-20 a las 16 31 23

After:

Captura de pantalla 2025-01-20 a las 16 32 02

Why did you choose this fix out of the possible options?

I chose this fix because it's the simplest approach. Maybe middleman or kramdown could do better at validating options, but I'm leaving it as is for now.

We're using options that are exclusive to that parser, so we should
explicitly force it.

Maybe middleman or kramdown could do better at validating options, but
I'm leaving it as is for now.
@simi simi merged commit 0acdd67 into master Jan 20, 2025
3 checks passed
@simi simi deleted the gfm branch January 20, 2025 15:47
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.

2 participants