Open
Conversation
595d9ea to
58b11cf
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
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.
Test:
Note
Medium Risk
Changes multipart field parsing for the filesystem upload endpoint, which could affect how file uploads are interpreted and written to disk if clients send ambiguous field names.
Overview
UploadFilesnow accepts a no-index multipart “comma” array format (files.fileandfiles.dest_path), treating it as index0in addition to the existing indexed field encodings.Adds a focused regression test (
TestUploadFilesCommaFormat) to verify the new field naming convention successfully uploads and writes the file to the requested destination.Written by Cursor Bugbot for commit 58b11cf. This will update automatically on new commits. Configure here.