added remark-gfm plugin to enable rendering markdown tables - #3965
Merged
Conversation
KoolADE85
reviewed
Aug 31, 2026
KoolADE85
left a comment
KoolADE85
left a comment
Contributor
There was a problem hiding this comment.
Great catch @AnnMarieW ! This looks good on my end.
We'd benefit from a test to prevent this from happening again. Otherwise, looks good on my end. Probably don't need a changelog entry.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #3964
PR #3960 updates
react-markdownfrom v4 to v8.As of
react-markdownv5, theremark-gfmplugin is required to render tables, strikethrough, task lists and other GitHub markdown features.This PR adds
remark-gfmversion 3.0.1 to be compatible withreact-markdownversion 8.0.7To do:
Since this is just an extension of PR #3960 which has not yet been released, is a changelog entry necessary?
Example from issue renders correctly now: