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

Swagger vs REST API: Interface.wireless_lans array #9173

New Issue
Closed
opened 2025-12-29 20:46:32 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:46:32 +01:00
Owner
Copy Link

Originally created by @janhlavin on GitHub (Jan 30, 2024).

Originally assigned to: @Smixi on GitHub.

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.11

Steps to Reproduce

  1. create wireless lan
  2. create device with interface
  3. associate wireless lan to interface

Expected Behavior

items in Interface.wireless_lans collection of WirelessLAN object in Swagger schema

Observed Behavior

items in Interface.wireless_lans collection of number in Swagger schema, but REST API return WirelessLAN objects

Originally created by @janhlavin on GitHub (Jan 30, 2024). Originally assigned to: @Smixi on GitHub. ### Deployment Type Self-hosted ### NetBox Version v3.7.1 ### Python Version 3.11 ### Steps to Reproduce 1. create wireless lan 2. create device with interface 3. associate wireless lan to interface ### Expected Behavior items in `Interface.wireless_lans` collection of **WirelessLAN** object in Swagger schema ### Observed Behavior items in `Interface.wireless_lans` collection of _number_ in Swagger schema, but REST API return **WirelessLAN** objects
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:46:32 +01:00
adam closed this issue 2025-12-29 20:46:32 +01:00
adam commented 2025-12-29 20:46:32 +01:00
Author
Owner
Copy Link

@Smixi commented on GitHub (Feb 4, 2024):

Hi, I made some investigation. All fields using SerializedPKRelatedField are correctly represented for the request, but doesn't use the serializer for response, this is because they are represented by drf-spectacular with the PrimaryKeyRelatedField. I can make a PR so it uses the same method described here : https://github.com/tfranzel/drf-spectacular/issues/778

@Smixi commented on GitHub (Feb 4, 2024): Hi, I made some investigation. All fields using `SerializedPKRelatedField` are correctly represented for the request, but doesn't use the serializer for response, this is because they are represented by drf-spectacular with the PrimaryKeyRelatedField. I can make a PR so it uses the same method described here : https://github.com/tfranzel/drf-spectacular/issues/778
adam commented 2025-12-29 20:46:32 +01:00
Author
Owner
Copy Link

@Smixi commented on GitHub (Mar 24, 2024):

Hi @abhi1693, do you have news ? I think the PR is ready if its ok for you

@Smixi commented on GitHub (Mar 24, 2024): Hi @abhi1693, do you have news ? I think the PR is ready if its ok for you
adam commented 2025-12-29 20:46:33 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Mar 25, 2024):

Looks like there is another PR #15449 that solves a similar issue.

@abhi1693 commented on GitHub (Mar 25, 2024): Looks like there is another PR #15449 that solves a similar issue.
adam commented 2025-12-29 20:46:33 +01:00
Author
Owner
Copy Link

@Smixi commented on GitHub (Mar 26, 2024):

Arf, it got duplicated. Did the other PR works ? I checked but it seems it doesn't looks for the direction value to use int for request.

@Smixi commented on GitHub (Mar 26, 2024): Arf, it got duplicated. Did the other PR works ? I checked but it seems it doesn't looks for the direction value to use int for request.
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 severity: low status: accepted type: bug
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#9173
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?