fix: URL encode paths in GitHub document loader #8847
Closed
Conversation
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
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
hntrl
approved these changes
Sep 5, 2025
Fix issue where directories with special characters (like '%5Fmeta') would cause 404 errors because paths were not properly URL encoded when constructing GitHub API requests. - Apply encodeURIComponent() to path parameter in fetchRepoFiles method - Add unit test to verify proper encoding of paths with special characters
hntrl
force-pushed
the
fix-github-loader-url-encoding
branch
from
a22ebe9 to
a1cf47a
Compare
|
not quite sure what happened here -- tried to rebase and github closed this. Continued on in #8860 |
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.
Fix issue where directories with special characters (like '%5Fmeta') would cause 404 errors because paths were not properly URL encoded when constructing GitHub API requests.