starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Rearchitect the logic for registering models & model features #9195

New Issue
Closed
opened 2025-12-29 20:46:49 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:46:49 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Feb 5, 2024).

Originally assigned to: @jeremystretch on GitHub.

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 the ready() 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.

Originally created by @jeremystretch on GitHub (Feb 5, 2024). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Currently, NetBox automatically registers all models and their features by hooking into Django's [`class_prepared`](https://docs.djangoproject.com/en/5.0/ref/signals/#class-prepared) signal. This issue proposes moving the registration triggers into the `ready()` 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.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 20:46:49 +01:00
adam closed this issue 2025-12-29 20:46:49 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: housekeeping
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9195
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?