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

Object-name scaling in rack-view #1828

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

Originally created by @netaviator on GitHub (Jul 6, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation
[ ] Housekeeping

Environment

  • Python version: 3.5.2
  • NetBox version: 2.3.2

Description

It would be nice if the object names in the rack view would scale depending on the count of units and the width of the box.
grafik

Originally created by @netaviator on GitHub (Jul 6, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> [ ] Housekeeping <!-- Changes pertaining to the codebase itself --> ### Environment * Python version: 3.5.2 * NetBox version: 2.3.2 ### Description It would be nice if the object names in the rack view would scale depending on the count of units and the width of the box. ![grafik](https://user-images.githubusercontent.com/8172056/42380400-1605259e-812e-11e8-839c-2eefb37bd89d.png)
adam closed this issue 2025-12-29 17:19:34 +01:00
adam commented 2025-12-29 17:19:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

I can't think of a way to accomplish this elegantly in the current setup. It might be feasible under #2248.

@jeremystretch commented on GitHub (Jul 18, 2018): I can't think of a way to accomplish this elegantly in the current setup. It might be feasible under #2248.
adam commented 2025-12-29 17:19:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2018):

#2248 actually looks pretty promising. Closing this out as I don't want to spend any effort on further tweaks to the current rendering approach.

@jeremystretch commented on GitHub (Jul 27, 2018): #2248 actually looks pretty promising. Closing this out as I don't want to spend any effort on further tweaks to the current rendering approach.
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
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#1828
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?