Skip to content

[Messenger] Describe resettable option for InMemoryTransport #17254

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.

Sign up for GitHub

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

Closed
wants to merge 2 commits into from
Closed

[Messenger] Describe resettable option for InMemoryTransport #17254

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5db161b
[Messenger] Describe resettable option for InMemoryTransport
alexndlm Sep 7, 2022
58451dc
Update messenger.rst
alexndlm Sep 7, 2022
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
9 changes: 9 additions & 0 deletions messenger.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1539,6 +1539,15 @@ The transport has a number of options:
Whether to serialize messages or not. This is useful to test an additional
layer, especially when you use your own message serializer.

``resettable`` (boolean, default: ``true``)
Whether to reset automatically during container resetting. This is useful
to have an option to check sent messages when running worker in tests with
``messenger.listener.reset_services`` subscriber.

.. versionadded:: 6.1

The ``resettable`` option was introduced in Symfony 6.1.

.. note::

All ``in-memory`` transports will be reset automatically after each test **in**
Expand Down