-
Notifications
You must be signed in to change notification settings - Fork 51
fix(loaders): restore a/b prefixes on noprefix patch input #240
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
Open
mo
wants to merge
2
commits into
modem-dev:main
Choose a base branch
from
mo:fix-noprefix-pager
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+196
−1
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blockNeedsPrefixis never cleared after the+++header, corrupting removals of--comment linesOnce the
+++file header is rewritten,blockNeedsPrefixstaystruefor the rest of the block. In a unified diff, a removed line whose content starts with--(SQL/Lua/Haskell/Ada comments are exactly this) produces a diff body line that begins with---(three dashes + space). This line is indistinguishable from the file header marker by the currentstartsWith("--- ")check, so it gets ana/prefix prepended — corrupting the diff before it reaches the parser. A minimal repro: any noprefix diff that removes a SQL comment like-- drop tablewill have a content line--- drop table, which becomes--- a/drop tableafter this rewrite. The parser will reject the mangled patch, andnormalizePatchChangesetwill swallow the error and returnfiles: [].Setting
blockNeedsPrefix = falseimmediately after the+++line is processed is sufficient; the---/+++pair is always the last pair of header lines before the first@@hunk marker in any valid git diff output.Prompt To Fix With AI