8000 [#10664] minor tweaks after merging into 4.2 · symfony/symfony-docs@c12928f · GitHub
[go: up one dir, main page]

Skip to content

Commit c12928f

Browse files
committed
[#10664] minor tweaks after merging into 4.2
1 parent 436cbd0 commit c12928f

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

components/messenger.rst

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -53,15 +53,15 @@ Concepts
5353
applicable throughout the application and affecting the entire message bus.
5454
For instance: logging, validating a message, starting a transaction, ...
5555
They are also responsible for calling the next middleware in the chain,
56-
which means they can tweak the envelope, by adding items to it or even
56+
which means they can tweak the envelope, by adding stamps to it or even
5757
replacing it, as well as interrupt the middleware chain.
5858

5959
**Envelope**
6060
Messenger specific concept, it gives full flexibility inside the message bus,
6161
by wrapping the messages into it, allowing to add useful information inside
62-
through *envelope items*.
62+
through *envelope stamps*.
6363

64-
**Envelope Items**
64+
**Envelope Stamps**
6565
Piece of information you need to attach to your message: serializer context
6666
to use for transport, markers identifying a received message or any sort of
6767
metadata your middleware or transport layer may use.
@@ -76,7 +76,7 @@ When using the message bus with Symfony's FrameworkBundle, the following middlew
7676
are configured for you:
7777

7878
#. :class:`Symfony\\Component\\Messenger\\Middleware\\LoggingMiddleware` (logs the processing of your messages)
79-
#. :class:`Symfony\\Component\\Messenger\\Asynchronous\\Middleware\\SendMessageMiddleware` (enables asynchronous processing)
79+
#. :class:`Symfony\\Component\\Messenger\\Middleware\\SendMessageMiddleware` (enables asynchronous processing)
8080
#. :class:`Symfony\\Component\\Messenger\\Middleware\\HandleMessageMiddleware` (calls the registered handler(s))
8181

8282
Example::
@@ -166,7 +166,7 @@ Hence you can inspect the envelope content and its stamps, or add any::
166166
if (null !== $envelope->get(ReceivedStamp::class)) {
167167
// Message just has been received...
168168

169-
// You could for example add another item.
169+
// You could for example add another stamp.
170170
$envelope = $envelope->with(new AnotherStamp(/* ... */));
171171
}
172172

@@ -176,12 +176,12 @@ Hence you can inspect the envelope content and its stamps, or add any::
176176

177177
The above example will forward the message to the next middleware with an additional
178178
stamp *if* the message has just been received (i.e. has the `ReceivedStamp` stamp).
179-
You can create your own items by implementing :class:`Symfony\\Component\\Messenger\\Stamp\\StampInterface`.
179+
You can create your own stamps by implementing :class:`Symfony\\Component\\Messenger\\Stamp\\StampInterface`.
180180

181181
.. note::
182182

183-
Any envelope item must be php serializable if going through transport using
184-
the :class:`Symfony\\Component\\Messenger\\Transport\\Serialization\\Serializer`
183+
Any stamp must be serializable using the Symfony Serializer component
184+
if going through transport using the :class:`Symfony\\Component\\Messenger\\Transport\\Serialization\\Serializer`
185185
base serializer.
186186

187187
Transports

0 commit comments

Comments
 (0)
0