fix: enable markdown line break rendering in about sections (#1713)#1816
Open
DukeDeSouth wants to merge 1 commit intoGreenstand:mainfrom
Open
fix: enable markdown line break rendering in about sections (#1713)#1816DukeDeSouth wants to merge 1 commit intoGreenstand:mainfrom
DukeDeSouth wants to merge 1 commit intoGreenstand:mainfrom
Conversation
…nd#1713) marked.parse() was called without the breaks option, so single newline characters in wallet/planter/organization about text were rendered as spaces instead of line breaks. Adding { breaks: true } makes marked treat single newlines as <br> tags (GFM-style), which correctly renders line breaks in the about and mission sections across all three entity pages.
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
1 participant
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.
The about sections on wallet, planter, and organization pages were rendering newline characters as spaces because marked.parse() was using default settings. The markdown parser treats single newlines as whitespace unless told otherwise, so text that should have been on separate lines was displayed as one continuous block. This fix adds the breaks option to all four marked.parse() calls across the three entity pages, which makes single newlines render as actual line breaks in the browser.
Closes #1713
Made with Cursor