Rearchitect the logic for registering models & model features #15042
Labels
status: accepted
This issue has been accepted for implementation
type: housekeeping
Changes to the application which do not directly impact the end user
Milestone
Proposed Changes
Currently, NetBox automatically registers all models and their features by hooking into Django's
class_prepared
signal. This issue proposes moving the registration triggers into theready()
method of the AppConfig class for each app.Justification
Although the current approach has generally worked well, issues arose while introducing a custom user model under #12795. Because Django must load the (now custom) user model before the signal handler, we must reorder the logic. This will also enable cleaner separation of functions.
The text was updated successfully, but these errors were encountered: