\nSupported variables:\n* `QVAL_MAKE_REQUEST_WRAPPER = myapp.myfile.my_func`. Customizes behaviour of the `make_request()` function, \nwhich is applied to all incoming requests, then the result is passed to `qval.qval.QueryParamValidator`. \nThe provided function must accept `request` and return object that supports request interface \n(see `qval.framework_integration.DummyReqiest`).\n
For example, the following code adds logging to each `make_request()` call:\n\n ```python\n # app/utils.py\n def my_wrapper(f):\n @functools.wraps(f)\n def wrapper(request):\n print(f\"Received new request: {request}\")\n return f(request)\n return wrapper\n ```\n You also need to execute `export QVAL_MAKE_REQUEST_WRAPPER=app.utils.my_wrapper` in your console\n or to add it to the config file.\n* `QVAL_REQUEST_CLASS = path.to.CustomRequestClass`. `@qval()` will use it to determine which argument is a request. \nIf you have a custom request class that implements `qval.framework_integration.DummyRequest` interface, provide it with this variable.\n\n* `QVAL_LOGGERS = [mylogger.factory, ...] | mylogger.factory`. List of paths or a path to a factory callable. \nSpecified callable must return object with the `Logger` interface. See section [logging](#logging) for more info.\n\n### Logging\nQval uses a global object called `log` acting as singleton when reporting errors. By default, `logging.getLogger` \nfunction is used as a factory on each call. You can provide your own factory (see [configuration](#configuration)) or disable logging. Example error message:\n```bash\nAn error occurred during the validation or inside of the context: exc `