mirror of
https://github.com/jazzband/django-auditlog.git
synced 2026-03-16 22:20:26 +00:00
Fix typo in usage.rst regarding field exclusion (#801)
Some checks failed
Test / SQLite • Python 3.10 (push) Has been cancelled
Test / SQLite • Python 3.11 (push) Has been cancelled
Test / SQLite • Python 3.12 (push) Has been cancelled
Test / SQLite • Python 3.13 (push) Has been cancelled
Test / PostgreSQL • Python 3.10 (push) Has been cancelled
Test / PostgreSQL • Python 3.11 (push) Has been cancelled
Test / PostgreSQL • Python 3.12 (push) Has been cancelled
Test / PostgreSQL • Python 3.13 (push) Has been cancelled
Test / MySQL • Python 3.10 (push) Has been cancelled
Test / MySQL • Python 3.11 (push) Has been cancelled
Test / MySQL • Python 3.12 (push) Has been cancelled
Test / MySQL • Python 3.13 (push) Has been cancelled
Some checks failed
Test / SQLite • Python 3.10 (push) Has been cancelled
Test / SQLite • Python 3.11 (push) Has been cancelled
Test / SQLite • Python 3.12 (push) Has been cancelled
Test / SQLite • Python 3.13 (push) Has been cancelled
Test / PostgreSQL • Python 3.10 (push) Has been cancelled
Test / PostgreSQL • Python 3.11 (push) Has been cancelled
Test / PostgreSQL • Python 3.12 (push) Has been cancelled
Test / PostgreSQL • Python 3.13 (push) Has been cancelled
Test / MySQL • Python 3.10 (push) Has been cancelled
Test / MySQL • Python 3.11 (push) Has been cancelled
Test / MySQL • Python 3.12 (push) Has been cancelled
Test / MySQL • Python 3.13 (push) Has been cancelled
This commit is contained in:
parent
6d170da5fc
commit
3f255a02d9
1 changed files with 1 additions and 1 deletions
|
|
@ -76,7 +76,7 @@ You can also add log-access to function base views, as the following example ill
|
||||||
|
|
||||||
Fields that are excluded will not trigger saving a new log entry and will not show up in the recorded changes.
|
Fields that are excluded will not trigger saving a new log entry and will not show up in the recorded changes.
|
||||||
|
|
||||||
To exclude specific fields from the log you can pass ``include_fields`` resp. ``exclude_fields`` to the ``register``
|
To exclude specific fields from the log you can pass ``include_fields`` or ``exclude_fields`` to the ``register``
|
||||||
method. If ``exclude_fields`` is specified the fields with the given names will not be included in the generated log
|
method. If ``exclude_fields`` is specified the fields with the given names will not be included in the generated log
|
||||||
entries. If ``include_fields`` is specified only the fields with the given names will be included in the generated log
|
entries. If ``include_fields`` is specified only the fields with the given names will be included in the generated log
|
||||||
entries. Explicitly excluding fields through ``exclude_fields`` takes precedence over specifying which fields to
|
entries. Explicitly excluding fields through ``exclude_fields`` takes precedence over specifying which fields to
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue