Repository navigation
feat: read a received email's MAP part and release 0.3.2 - #14
Merged
Merged
Conversation
extractMessage() and `mailschema message <message.eml>` find an email's one MAP part from its original bytes, with the rules of the Ruby package's Message.extract. Enum and const errors name their allowed values, and the README says where contracts live. Prepared from mailschema/mailschema@1b41186.
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.
Prepared from mailschema/mailschema@1b41186 (mailschema/mailschema#36) by
npm run packages:upstream.extractMessage(input)andmailschema message <message.eml>find a received email's one MAP part from its original bytes, with the same rules and reasons as the Ruby package'sMessage.extract.Tests: 5 of 5 pass, including the CLI
messagerun against the publishedpublication.eml.dist/was rebuilt.