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

Create tests for natural ordering #1739

New Issue
Closed
opened 2025-12-29 16:34:53 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:34:53 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (May 23, 2018).

Issue type

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

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.3

Description

We seem to have recurring issues with the logic NetBox uses to effect natural ordering of object lists, particularly device interfaces. We need to establish a set of tests that define the expected order of objects using a variety of different naming schemes. This will make it easier to identify cases not covered by the existing logic.

Originally created by @jeremystretch on GitHub (May 23, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: 2.2.3 ### Description We seem to have [recurring issues](https://github.com/digitalocean/netbox/issues?utf8=%E2%9C%93&q=is%3Aissue+natural+ordering) with the logic NetBox uses to effect natural ordering of object lists, particularly device interfaces. We need to establish a set of tests that define the expected order of objects using a variety of different naming schemes. This will make it easier to identify cases not covered by the existing logic.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 16:34:53 +01:00
adam closed this issue 2025-12-29 16:34:53 +01:00
adam commented 2025-12-29 16:34:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 8, 2018):

Implemented some basic tests in 048e843c39 but will probably end up substantially reworking NaturalOrderByManager.

@jeremystretch commented on GitHub (Jun 8, 2018): Implemented some basic tests in 048e843c3925f061e620770477ace9ed4b5e3a33 but will probably end up substantially reworking NaturalOrderByManager.
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: housekeeping
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#1739
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?