fix: send displayName/mimeType in uploadToFileSearchStore body (fileSearchStores) #1135
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.
Problem
When uploading a document to a File Search store via
uploadToFileSearchStoreusing aBlob, the SDK does not senddisplayName(and related metadata) in the request body used to obtain the upload URL. As a result, created documents can end up with undefined and downstream retrieval/citations lose the friendly name.Current Behavior
config.displayNameis accepted by the SDK call, but the value is not forwarded into theuploadToFileSearchStorerequest body.displayName: (no display name)even though the caller set it.Expected Behavior
displayNameprovided inconfigshould be persisted as the created document’s display name.mimeTypeprovided inconfigshould be forwarded consistently as part of the request metadata.Fix
displayNameandmimeTypeto the JSON request body passed to theuploadToFileSearchStoreendpoint when generating the upload URL.displayNameandmimeType).