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

Expose depth and child count on prefix REST API serializer #4948

New Issue
Closed
opened 2025-12-29 19:22:34 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:22:34 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (May 28, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.4

Feature type

Change to existing functionality

Proposed functionality

Add two read-only fields to the REST API serializer for the ipam.Prefix model:

  • _depth: Depth in the prefix hierarchy (e.g. a root-level prefix will have a depth of zero)
  • children: The number of child prefixes contained within this prefix

The leading underscore in the name of the depth field is consistent with models which employ MPTT to maintain a hierarchy, such as dcim.Region.

Use case

Following the work implemented under #6087, it is now possible to include this data with no performance impact.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (May 28, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.4 ### Feature type Change to existing functionality ### Proposed functionality Add two read-only fields to the REST API serializer for the ipam.Prefix model: - `_depth`: Depth in the prefix hierarchy (e.g. a root-level prefix will have a depth of zero) - `children`: The number of child prefixes contained within this prefix The leading underscore in the name of the depth field is consistent with models which employ MPTT to maintain a hierarchy, such as dcim.Region. ### Use case Following the work implemented under #6087, it is now possible to include this data with no performance impact. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:22:34 +01:00
adam closed this issue 2025-12-29 19:22:34 +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: 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#4948
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?