Skip to content
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

Default to printing emails to logs in development #555

Merged
merged 1 commit into from Sep 25, 2020
Merged

Default to printing emails to logs in development #555

merged 1 commit into from Sep 25, 2020

Conversation

stephendolan
Copy link
Member

This PR aims to make debugging emails a bit more straightforward for new Lucky users. I remember being quite confused the first time I tried to send an email in dev and ended up enabling SendGrid since I couldn't determine how to show the email content.

Since then, I've dug into the Carbon source and found the nifty print_emails option when initializing a Carbon::DevAdapter! I think it'd be handy to turn that on by default in dev, especially since if it's too noisy turning the flag off is pretty straightforward.

If this isn't agreeable, there are a few other options that could help (that I'm happy to open issues/PRs for):

  • Add documentation for the print_emails flag to the Carbon readme
  • Add documentation for the print_emails flag to the Lucky guides

This PR aims to make debugging emails a bit more straightforward for more Lucky users. I remember being quite confused the first time I tried to send an email in dev, and ended up enabling SendGrid since I couldn't determine how to show the email content.

Since then, I've dug into the Carbon source and found the nifty `print_emails` option when initializing a `Carbon::DevAdapter`! I think it'd be handy to turn that on by default in dev, especially since if it's too noisy turning the flag off is pretty straightforward.
Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you open an issue on the website to document this? I know those guides are lacking a lot, but it'll be nice to start tracking some of that.

Copy link
Member

@paulcsmith paulcsmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good idea for now, but hopefully soonish we'll have Breeze and Pulsar hooked up so it will print a link to the logs that will tka you to a page with the email that was sent in dev!

@jwoertink jwoertink merged commit 63865e7 into luckyframework:master Sep 25, 2020
@stephendolan
Copy link
Member Author

Will do, @jwoertink.

Can't wait, that sounds super convenient @paulcsmith!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants