-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Removed Mailer component docs #13945
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
Conversation
2858190
to
868c0bd
Compare
868c0bd
to
5dd6757
Compare
5dd6757
to
225de94
Compare
Oh, I'm sorry for the countless copy-paste mistakes. Thanks for your detailed review! |
This PR was merged into the 4.4 branch. Discussion ---------- [Mailer] Updated README for the Mailer component | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | n/a | License | MIT | Doc PR | symfony/symfony-docs#13945 I think it's worth adding a second example showcasing the twig integration for 2 reasons: * If you're used to use this component in the framework, I think it's likely you want Twig integration in standalone apps. * The integration actually lives in `symfony/twig-bridge`, it won't be very easy to catch while reading the component code - unless you're very comfortable with the Symfony architecture. Commits ------- 696560c Updated README for the Mailer component
This PR was merged into the 4.4 branch. Discussion ---------- [Mailer] Updated README for the Mailer component | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | n/a | License | MIT | Doc PR | symfony/symfony-docs#13945 I think it's worth adding a second example showcasing the twig integration for 2 reasons: * If you're used to use this component in the framework, I think it's likely you want Twig integration in standalone apps. * The integration actually lives in `symfony/twig-bridge`, it won't be very easy to catch while reading the component code - unless you're very comfortable with the Symfony architecture. Commits ------- 696560c690 Updated README for the Mailer component
The change upstream has been merged now. |
Thank you Wouter. |
This change completely removed this paragraph from the documentation. |
Hi @oxan! The null DSN is documented here: https://symfony.com/doc/current/mailer.html#disabling-delivery |
@wouterj Sorry, I was too curt with my comment. What I meant was that the sendmail DSN isn't documented anymore. |
No problem @oxan, thanks for clarifying :) I think I removed it in favor of this section https://symfony.com/doc/current/mailer.html#transport-setup . That section doesn't explicitly say "sendmail", but what it shows (native SMTP) is in fact sendmail. If you think we should be more explicit about it, please consider hitting the "edit this page" button at the top right. (btw, from my understanding, |
@wouterj As I understand the code (I haven't actually verified this), I think it'd be ideal to have a subsection for every transport along with the required parameters and the available options, but that'd be a quite involved change. |
This PR was merged into the 4.4 branch. Discussion ---------- [Mailer] Updated README for the Mailer component | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | n/a | License | MIT | Doc PR | symfony/symfony-docs#13945 I think it's worth adding a second example showcasing the twig integration for 2 reasons: * If you're used to use this component in the framework, I think it's likely you want Twig integration in standalone apps. * The integration actually lives in `symfony/twig-bridge`, it won't be very easy to catch while reading the component code - unless you're very comfortable with the Symfony architecture. Commits ------- 696560c690 Updated README for the Mailer component
See symfony/symfony#37542
The component is quite easy to use in a standalone project. The example in the component's README will be enough I think (no need to confuse framework users by adding the examples in this doc).
Meanwhile, I'm not sure what to do with the Mime component. Should we move it into a subguide (
/mailer/mime.rst
)? It doesn't really make sense to have it as a main guide I think.