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

Rename CustomField object_type to related_object_type #9326

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

Originally created by @jeremystretch on GitHub (Mar 6, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.7.3

Feature type

Change to existing functionality

Proposed functionality

Rename the object_type ForeignKey field on CustomField to related_object_type (or any better suggestion).

Use case

Following the renaming of the content_types ManyToManyField to object_types under #15277, the name object_type can now be quite confusing. (object_types defines the types of NetBox objects on which the field appears, whereas object_type indicates the model indicated by an object or multi-object field.) Renaming this field should help avoid user confusion.

Database changes

Rename the object_type ForeignKey field on the CustomField model (effecting a migration).

External dependencies

None

Originally created by @jeremystretch on GitHub (Mar 6, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.7.3 ### Feature type Change to existing functionality ### Proposed functionality Rename the `object_type` ForeignKey field on CustomField to `related_object_type` (or any better suggestion). ### Use case Following the renaming of the `content_types` ManyToManyField to `object_types` under #15277, the name `object_type` can now be quite confusing. (`object_types` defines the types of NetBox objects on which the field appears, whereas `object_type` indicates the model indicated by an object or multi-object field.) Renaming this field should help avoid user confusion. ### Database changes Rename the `object_type` ForeignKey field on the CustomField model (effecting a migration). ### External dependencies None
adam added the status: acceptedtype: featurebreaking change labels 2025-12-29 20:48:32 +01:00
adam closed this issue 2025-12-29 20:48:32 +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 breaking change status: accepted type: feature
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#9326
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?