[ISSUE-41] Bugfix: Parsing text/plain
and text/html
attachments
#44
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.
Rationale
As reported by @naidishuli in #41, we have been parsing
text/plain
andtext/html
attachments incorrectly. Even when they are attached with theContent-Disposition: attachment
header, we mistakenly treat them as text and HTML content, respectively.This PR addresses and resolves this problem.
Commits:
text/plain
and atext/html
content-disposition: attachment
files.letters_test.go
to expect text/plain and text/html attachments to be correctly parsed.parsePart()
to correctly handle attachments of any content type.parsePart()
loop.isInlineFile()
andisAttachedFile()
to not parse Content Disposition header multiple times.