Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Swiftmailer spool collector#84

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
dator-zz wants to merge2 commits intosymfony:masterfromdator-zz:swiftmailer_spool_collector
Closed

Swiftmailer spool collector#84

dator-zz wants to merge2 commits intosymfony:masterfromdator-zz:swiftmailer_spool_collector

Conversation

dator-zz
Copy link

This commit add a DataCollector for Swiftmailer spool with the number of messages in the spool.

I choose an icon in iconfinder.com, if you have a better one :)

@stof
Copy link
Member

A great thing would be to have a DataCollector showing the email sent as it would be easier to debug the mailing.

Your implementation is not good as it does not collect the data about the current request. The spooled messages can concern another request.

@dator-zz
Copy link
Author

Mmm ok I see, so you are saying that showing spooled messages is not required but you prefer to have the webprofiler showing the current email sent ?

@stof
Copy link
Member

Yes. The profiler is about collecting data on the current request:http://docs.symfony-reloaded.org/master/guides/internals/profiler.html so a Swiftmailer DataCollector should respect this design.

But showing the email sent can be more difficult. I don't know if Swiftmailer provide an extension point to log the email sent (which would allow to collect them by logging in an array just like Doctrine and the Logger do for the profiler).

@fabpot
Copy link
Member

@stof: We have such an implementation in symfony1, so it is definitely possible.
@dator: Have a look at the symfony1 code for inspiration.

@fabpot
Copy link
Member

I'm closing this PR as the current implementation cannot be merged as is.

SofHad pushed a commit to SofHad/symfony that referenced this pull requestOct 12, 2015
…ndre)This PR was merged into the master branch.Discussion----------Added Brazilian Portuguese translationsHi!Here is a complete Brazilian Portuguese translationCommits-------233ade0 Added Brazilian Portuguese translations
jderusse pushed a commit to jderusse/symfony that referenced this pull requestMar 30, 2020
…sories#12-yaml-syntax-fixesCorrecting YAML syntax for branch names
derrabus pushed a commit to derrabus/symfony that referenced this pull requestJul 25, 2023
derrabus pushed a commit to derrabus/symfony that referenced this pull requestJul 25, 2023
…ersion (iluuu1994)This PR was merged into the 2.0-dev branch.Discussion----------Fix BinaryFileResponse with range to psr response conversionClosessymfony#84As requested by [Fabien](symfony#38280 (comment)).I think using the slightly less optimal version of checking for a `Content-Range` header is better than relying on reflection. In theory, this could be slightly sub optimal when streaming whole files and setting the `Content-Range` manually but I'm assuming that's very rare in practice.Commits-------5d5932d Fix BinaryFileResponse with range to psr response conversion
stobrien89 pushed a commit to stobrien89/symfony that referenced this pull requestFeb 27, 2025
Increase minimum version minor version of PHPUnit version 5
This pull request wasclosed.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@dator-zz@stof@fabpot@dator

[8]ページ先頭

©2009-2025 Movatter.jp