Skip to content

Commit f922176

Browse files
Matthew WeppennaarMatthew Weppennaar
authored andcommitted
fixing docs
1 parent eec2830 commit f922176

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

docs/middleware/building_your_own_middleware.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
Implementing your own middleware
2-
==========
2+
=================================
33

44
A middleware class provides three handler functions, one for processing each of the three kinds of messages transports, applications and dispatchers typically send and receive (i.e. inbound user messages, outbound user messages, event messages) and three enabled functions for each of the types of messages
55

@@ -51,6 +51,7 @@ Processes the message before passing it to the next handler.
5151
Example of a simple middleware implementation from ``vumi2.middlewares.logging:``
5252

5353
.. code-block:: python
54+
:caption: logging middleware
5455
from logging import getLevelNamesMapping, getLogger
5556
5657
from attr import define
@@ -88,7 +89,7 @@ Example of a simple middleware implementation from ``vumi2.middlewares.logging:`
8889
return self._log_msg("event", event, connector_name)
8990
9091
How your middleware is used inside Vumi:
91-
-----------------
92+
----------------------------------------
9293

9394
While writing complex middleware, it may help to understand how a middleware class is used by Vumi transports and applications.
9495

0 commit comments

Comments
 (0)