Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent display of IP family on aggregate API serializer #3930

Closed
jeremystretch opened this issue Jan 15, 2020 · 0 comments
Closed

Inconsistent display of IP family on aggregate API serializer #3930

jeremystretch opened this issue Jan 15, 2020 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@jeremystretch
Copy link
Member

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.12

Steps to Reproduce

  1. Request a prefix object via the REST API
  2. Request an aggregate object via the REST API

Expected Behavior

The family field for both objects should have the same format.

Observed Behavior

The prefix serializer renders family using a choice dictionary:

    "family": {
        "value": 4,
        "label": "IPv4"
    },

However, the aggregate serializer does not:

    "family": 4,

AggregateSerializer should be corrected to display the IP address family in the same manner as the prefix and IP address serializers.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation API change labels Jan 15, 2020
@jeremystretch jeremystretch self-assigned this Jan 15, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

1 participant