chore: Add EMAIL_FROM_NAME to .env.example #378
Conversation
This file contains 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.
This PR adds the
EMAIL_FROM_NAMEfield to the .env.example file.Why?
To maintain consistency in the "From" field of outgoing emails. Without setting
EMAIL_FROM_NAME, emails may appear with different senders, such asCal.com <[email protected]>orLoggedInUser <[email protected]>.After some trial and error, I discovered that both
EMAIL_FROMandEMAIL_FROM_NAMEneed to be defined for consistent email formatting, though this was not previously documented. Adding this to the example environment file ensures that developers are aware of it and can set it appropriately.