b733bca197
Spreading module callback registration across the codebase is both a bit messy and makes it unclear where a user should register callbacks if they want to define a new class of callbacks. Consolidating these under the synapse.module_api module cleans things up a bit, puts related code in the same place and makes it much more obvious how to extend it.
26 lines
881 B
Python
26 lines
881 B
Python
# Copyright 2023 The Matrix.org Foundation C.I.C.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
from .account_validity_callbacks import AccountValidityModuleApiCallbacks
|
|
|
|
__all__ = [
|
|
"AccountValidityModuleApiCallbacks",
|
|
"ModuleApiCallbacks",
|
|
]
|
|
|
|
|
|
class ModuleApiCallbacks:
|
|
def __init__(self) -> None:
|
|
self.account_validity = AccountValidityModuleApiCallbacks()
|