From 74b65bfc5f3c58005e3892b314e73cfde32355f6 Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Tue, 2 Nov 2021 14:27:50 +0000 Subject: deploy: 2d44ee6868805d4ff23489a8dd6b4072ff358663 --- latest/modules/writing_a_module.html | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'latest/modules/writing_a_module.html') diff --git a/latest/modules/writing_a_module.html b/latest/modules/writing_a_module.html index 5ea7d0b812..c91d9ec9b3 100644 --- a/latest/modules/writing_a_module.html +++ b/latest/modules/writing_a_module.html @@ -99,7 +99,7 @@ @@ -192,6 +192,17 @@ either the output of the module's parse_config static method (see b configuration associated with the module in Synapse's configuration file.

See the documentation for the ModuleApi class here.

+

When Synapse runs with several modules configured

+

If Synapse is running with other modules configured, the order each module appears in +within the modules section of the Synapse configuration file might restrict what it can +or cannot register. See this section for more +information.

+

On top of the rules listed in the link above, if a callback returns a value that should +cause the current operation to fail (e.g. if a callback checking an event returns with a +value that should cause the event to be denied), Synapse will fail the operation and +ignore any subsequent callbacks that should have been run after this one.

+

The documentation for each callback mentions how Synapse behaves when +multiple modules implement it.

Handling the module's configuration

A module can implement the following static method:

@staticmethod
-- 
cgit 1.5.1