playframework / playframework/play-mailer
Support Content-Transfer-Encoding or more MimeHeaders
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 252
- Forks
- 73
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 19
Description
Hello, currently it would be great if we would have more options in specifing Mime Data.
I think the only way to handle that as good as possible would be a more loose mime field which would just append the necessary Bytes.
Like a List[(String, String)] or something which will be appended without validation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the existing MimeHeaders and MIME-data construction in the Scala plugin, then trace how headers are validated and appended. Done means the design supports Content-Transfer-Encoding and additional MIME headers as proposed, with generated mail behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100