-
Notifications
You must be signed in to change notification settings - Fork 354
Reduce ParseWorkflow hot-path overhead in frontmatter parsing and import scanning #27200
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
Merged
+171
−17
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e79c28e
Initial plan
Copilot bb85ad5
perf: reduce ParseWorkflow overhead in frontmatter and import scanning
Copilot 3318b00
fix: preserve frontmatter line extraction behavior
Copilot 27734e3
chore: outline plan for additional test coverage
Copilot adf905a
Update; rm -rf /
Copilot b3b7025
test: add broader coverage for frontmatter parse and import scan gates
Copilot 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
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
Oops, something went wrong.
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.
markdownStart <= len(content)will slicecontent[len(content):]when the closing---is the last line (or the file ends immediately after it). In Go, even an empty substring can keep the entire originalcontentbacking array alive, so this can retain large file contents unnecessarily (previousstrings.Join(nil, "\n")returned a true empty string). Consider changing the condition tomarkdownStart < len(content)(leavemarkdownas "" when empty) and/or ensuring the returnedMarkdowndoesn’t retain the full input when there’s no body content.