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

Move the object types REST API endpoint to the core app #11354

New Issue
Closed
opened 2025-12-29 21:44:05 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:44:05 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jul 8, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.3.3

Feature type

Change to existing functionality

Proposed functionality

Move the REST API endpoint for object types from /api/extras/object-types/ to /api/core/object-types/. We can implement a redirect at the old endpoint to ensure backward compatibility.

(This FR was prompted by FR #19722.)

Use case

The current endpoint is outdated; it was originally implemented to serve Django's native ContentType model. However, in recent releases ObjectType, a proxy model within NetBox's core app, has superseded ContentType, and the REST API endpoint should be moved to reflect this.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Jul 8, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.3.3 ### Feature type Change to existing functionality ### Proposed functionality Move the REST API endpoint for object types from `/api/extras/object-types/` to `/api/core/object-types/`. We can implement a redirect at the old endpoint to ensure backward compatibility. (This FR was prompted by FR #19722.) ### Use case The current endpoint is outdated; it was originally implemented to serve Django's native ContentType model. However, in recent releases ObjectType, a proxy model within NetBox's `core` app, has superseded ContentType, and the REST API endpoint should be moved to reflect this. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:44:05 +01:00
adam closed this issue 2025-12-29 21:44:06 +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 complexity: low 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#11354
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?