Skip to content

Symfony Messenger component documentation #9437

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 15 commits into from
Apr 16, 2018
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update typos and missing reference
  • Loading branch information
sroze committed Mar 27, 2018
commit 2493c9087cf203134ae8112b2878c4537a73842c
13 changes: 4 additions & 9 deletions components/messenger.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,13 +38,13 @@ Concepts
Bus
---

The bus is used to dispatch messages. MessageBus' behavior is in its ordered
The bus is used to dispatch messages. MessageBus' behaviour is in its ordered
middleware stack. When using the message bus with Symfony's FrameworkBundle, the
following middlewares are configured for you:

#. ``LoggingMiddleware`` (logs the processing of your messages)
#. ``SendMessageMiddleware`` (enables asynchronous processing)
#. ``HandleMessageMiddleware`` (calls the registered handle)
#. :code:`LoggingMiddleware` (logs the processing of your messages)
#. :code:`SendMessageMiddleware` (enables asynchronous processing)
#. :code:`HandleMessageMiddleware` (calls the registered handle)

Example::

Expand Down Expand Up @@ -176,11 +176,6 @@ First, create your receiver::
}
}

Your adapter factory
~~~~~~~~~~~~~~~~~~~~

TODO.

Same bus received and sender
Copy link
Member

Choose a reason for hiding this comment

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

Capitalize.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
10 changes: 6 additions & 4 deletions messenger.rst
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ Adapters
--------

The communication with queuing system or third parties is delegated to
libraries for now. The `built-in AMQP adapter`_ allows you to communicate with
libraries for now. The built-in AMQP adapter allows you to communicate with
most of the AMQP brokers such as RabbitMQ.

.. note::
Expand Down Expand Up @@ -167,14 +167,16 @@ like this:
$ bin/console messenger:consume-messages messenger.default_receiver

The first argument is the receiver's service name. It might have been created by
your :code:`adapaters` configuration or it can be your own receiver.
your :code:`adapters` configuration or it can be your own receiver.

Your own Adapters
-----------------

Learn how to build your own adapters within the Component's documentation. Once
Copy link

Choose a reason for hiding this comment

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

Learn how to build your own adapters within the Component's documentation.

It is unclear what is meant by this!

you have built your classes, you can register your adapater to be able to use
it via a DSN in the Symfony application.
you have built your classes, you can register your adapter factory to be able to
use it via a DSN in the Symfony application.
Copy link

Choose a reason for hiding this comment

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

Where can I read about how to do this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In the "Use your adapter" section :)




Register your factory
Copy link
Member

Choose a reason for hiding this comment

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

s/f/F/

~~~~~~~~~~~~~~~~~~~~~
Expand Down