feat: support document MIME types (PDF, Office, etc) and set FileName on DocumentMessage - #342
Open
pokus32 wants to merge 1 commit into
Open
Conversation
… on DocumentMessage
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
1 participant
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.
Summary of Changes
.pdf,.docx,.xlsx,.pptx,.txt,.csv,.zip) insendWhatsAppMessage. Previously, all non-image/audio/video files defaulted toapplication/octet-stream.FileNameProtobuf Field: SetFileName: proto.String(fileName)onwaProto.DocumentMessage. Without this field and valid MIME type, WhatsApp mobile/desktop clients render documents as raw binary (.bin) blobs without extension badges or file previews.Tested sending PDF and office documents; now rendered correctly with PDF badge and inline viewer support.