CGM_Public/pretix_cgo
1
0
Fork 0
forked from CGM_Public/pretix_original
Code Pull Requests Actions Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Raphael Michel <michel@rami.io>
This commit is contained in:
Mira
2024-12-19 17:26:38 +01:00
committed by GitHub
parent 7b8783e089
commit 3b5630a66c
4 changed files with 27 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/development/api/plugins.rst
View File

@@ -121,7 +121,7 @@ This will automatically make pretix discover this plugin as soon as it is instal
through ``pip``. During development, you can just run ``python setup.py develop`` inside
your plugin source directory to make it discoverable.
.. _`Signals`:
.. _`signals`:
Signals
-------
@@ -163,7 +163,7 @@ ticket renderer.
However, for some of them (types of :ref:`Log Entries <logging>`) we use a different method to keep track of them:
In a ``Registry``, classes are collected at application startup, along with a unique key (in case
of LogEntryType, the action_type) as well as which plugin registered them.
of LogEntryType, the ``action_type``) as well as which plugin registered them.
To register a class, you can use one of several decorator provided by the Registry object:
@@ -174,7 +174,7 @@ To register a class, you can use one of several decorator provided by the Regist
pass
All files in which classes are registered need to be imported in the ``AppConfig.ready`` as explained
in `Signals`_ above.
in `Signals <signals>`_ above.
Views
-----