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

Type Hint for connected_endpoint Object #2178

New Issue
Closed
opened 2025-12-29 17:23:02 +01:00 by adam · 0 comments
adam commented 2025-12-29 17:23:02 +01:00
Owner
Copy Link

Originally created by @zachmoody on GitHub (Dec 6, 2018).

Environment

  • Python version: 3.6
  • NetBox version: 2.5-beta

Proposed Functionality

Add a field that provides a hint regarding what type of connection it is. Currently we can either get a device or circuit nested object. The addition of this always-present field could lend a hint to clients about which one to expect.

Use Case

When inspecting an interface return some clients may need to explicitly know whether to expect a device or circuit nested object in connected_endpoint.

Database Changes

None I'm aware of.

External Dependencies

None.

Originally created by @zachmoody on GitHub (Dec 6, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.5-beta <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add a field that provides a hint regarding what type of connection it is. Currently we can either get a `device` or `circuit` nested object. The addition of this always-present field could lend a hint to clients about which one to expect. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When inspecting an interface return some clients may need to explicitly know whether to expect a `device` or `circuit` nested object in `connected_endpoint`. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None I'm aware of. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 17:23:02 +01:00
adam closed this issue 2025-12-29 17:23:02 +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#2178
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?