history.checks

Overview

System checks for the history backend's configuration.

check_history_middleware

Report a middleware stack that cannot name the action behind a request.

get_defaults places the middleware correctly, but a project owns its own MIDDLEWARE and can replace or reorder that list. Both faults here are warnings rather than errors, because a request still records its events either way. What goes missing is the identity associating the events of one request with each other, or the user who caused them.

Any HistoryMiddleware subclass satisfies this, because a project may extend VUEDA's to record metadata of its own.

Signature

check_history_middleware(app_configs, kwargs)

Parameters

Name	Type	Required	Description
app_configs		yes
kwargs		yes

Source

server/vueda/history/checks.py:25

Source

server/vueda/history/checks.py