Eliminate obsolete "detail" versions of model tables #5384

Closed
opened 2025-12-29 19:27:22 +01:00 by adam · 0 comments
Owner

Originally created by @jeremystretch on GitHub (Sep 17, 2021).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

Historically, NetBox has declared two types of table classes for some models: brief and detailed. For example, dcim.tables.racks defines both RackTable and RackDetailTable (which inherits from RackTable). This issue proposes converging all such instances into a single table with all available fields.

Justification

This differentiation was made in the past primary to represent less-extensive representations of child or related objects. However, with the recent implementation of dynamically configurable tables, this is no longer needed.

Originally created by @jeremystretch on GitHub (Sep 17, 2021). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Historically, NetBox has declared two types of table classes for some models: brief and detailed. For example, `dcim.tables.racks` defines both RackTable and RackDetailTable (which inherits from RackTable). This issue proposes converging all such instances into a single table with all available fields. ### Justification This differentiation was made in the past primary to represent less-extensive representations of child or related objects. However, with the recent implementation of dynamically configurable tables, this is no longer needed.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 19:27:22 +01:00
adam closed this issue 2025-12-29 19:27:23 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5384