Closed
Conversation
- Add `from: Option<String>` to email Config struct - Treat empty/whitespace `from` as unconfigured, falling back to `username` - Replace `.unwrap()` with `?` on mailbox parse to propagate errors via Result - Update config.toml comment: clarify field must be absent (not empty) to use username fallback
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.
from字段用于设置发件地址 #378email.rs: addfrom: Option<String>field; treat empty/whitespace as unconfigured; replace.unwrap()and.expect()with?/.context()to propagate parse errorsconfig.toml: update comment to clarify that the field must be absent (not empty) to useusernameas fallback