-
Notifications
You must be signed in to change notification settings - Fork 28
Remove ActionMailer as a dependency #77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,3 +10,5 @@ gem "rake", "~> 13.0" | |
| gem "minitest", "~> 5.0" | ||
|
|
||
| gem "standard", "~> 1.3" | ||
|
|
||
| gem "actionmailer", ">= 7.0" | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Zeitwerk of course complains if the class is not defined. I looked if I could exclude only this class from eager_loading and requiring it manually only if ActionMailer::Base is defined, but I did not figure out how. Yes, it smells a bit to be honest, so I could investigate more if you think I should. |
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is what I'd do: immediatly check if we want to send emails but ActionMailer is not there: show a nice error message and explain how it can be fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it as a development dependency anyway