fix(review): make markdown formatting explicit#394
Open
onmax wants to merge 2 commits intonuxt-content:mainfrom
Open
fix(review): make markdown formatting explicit#394onmax wants to merge 2 commits intonuxt-content:mainfrom
onmax wants to merge 2 commits intonuxt-content:mainfrom
Conversation
Contributor
|
@onmax is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
onmax
force-pushed
the
fix/review-formatting-explicit
branch
from
a20cf35 to
e59da1b
Compare
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.
Summary
This PR makes markdown formatting rewrites explicit in review and keeps the original repo markdown source on first open in the md editor.
Opening a pristine repo-backed markdown file no longer creates a draft change just by initializing the editor.
It also includes the document comparison normalization needed so equivalent generated content is treated as unchanged.
Refs #382.
Validation
Covers the formatting review flow, pristine open behavior, and normalized document comparison with targeted tests.