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

Appearance settings

Middleware clarification about being called on "receive" #12535

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

Merged
merged 1 commit into from
Dec 11, 2019

Conversation

weaverryan
Copy link
Member

Hi!

A clarification that middleware may be called twice. I think this is the best spot, and isn't too big or too small.

@B-Galati
Copy link
Contributor

Thanks @weaverryan! Few questions on my end:

  • Should it also be documented in the component section?
  • Should built-in middlewares document their behavior about this? I think they should on my end to avoid having to look at the middlewares' code.

@weaverryan
Copy link
Member Author

Should it also be documented in the component section

I added some details there, but it was actually already shown in an example.

Should built-in middlewares document their behavior about this?

What do you mean by this?

@B-Galati
Copy link
Contributor

B-Galati commented Oct 22, 2019

Should built-in middlewares document their behavior about this?

What do you mean by this?

For example the doctrine ping connection middleware should say that it is triggered only when the message is handled by the worker otherwise it will do nothing.

It's a bit out of the scope of this PR though.

@weaverryan
Copy link
Member Author

For example the doctrine ping connection middleware should say that it is triggered only when the message is handled by the worker otherwise it will do nothing.

Perhaps - it would be a comment in the core class. But the class is also pretty small, and if you're wiring it up manually (e.g. not using the DoctrineBundle integration), then you'll probably look inside the class anyways. It doesn't seem too important to me to document anywhere.

components/messenger.rst Show resolved Hide resolved
@javiereguiluz javiereguiluz force-pushed the middleware-clarification branch from 14f6c5b to b9f315f Compare December 11, 2019 16:11
@javiereguiluz
Copy link
Member

Thanks Ryan.

javiereguiluz added a commit that referenced this pull request Dec 11, 2019
… (weaverryan)

This PR was squashed before being merged into the 4.3 branch (closes #12535).

Discussion
----------

Middleware clarification about being called on "receive"

Hi!

A clarification that middleware may be called twice. I think this is the best spot, and isn't too big or too small.

Commits
-------

b9f315f Middleware clarification about being called on \"receive\"
@javiereguiluz javiereguiluz merged commit b9f315f into symfony:4.3 Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.