Normalize post body_markdown newlines - #2119
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…ax/2115/normalise-newlines-in-database
cellio
approved these changes
Jul 30, 2026
cellio
left a comment
cellio
left a comment
Member
There was a problem hiding this comment.
Tested locally with the post that was failing in prod.
Oaphi
approved these changes
Jul 30, 2026
This was referenced Jul 31, 2026
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
3 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.
Fixes #2115
Normalizes the
body_markdownfield in the post model so that newlines are all\n.Applied only to this one field that was raised in #2115 for now, but let me know any other places you would also like to see this normalization, or if there's a preferred general approach. Provided your suggested approach doesn't clash with this, I'm hoping to get the specific fix merged and deployed first, then apply anything further separately once the bug is no longer holding up a question being posted.