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

Tags WebUI count doesn't match API #3116

Closed
pm17788 opened this issue Apr 26, 2019 · 1 comment
Closed

Tags WebUI count doesn't match API #3116

pm17788 opened this issue Apr 26, 2019 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@pm17788
Copy link

pm17788 commented Apr 26, 2019

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.8

Steps to Reproduce

  1. Browse to: https://NetBoxURL/extras/tags, see count of tags (ex: 25)
  2. Browse to: https://NetBoxURL/api/extras/tags, see count which is an aggregate of all tagged items, rather then the count of distinct tags in NetBox

Expected Behavior

API count of tags should match the WebUI and the API

Observed Behavior

API count of tags doesn't match the WebUI, or the behavior of count variable on other API endpoints.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Apr 26, 2019
@pm17788
Copy link
Author

pm17788 commented May 9, 2019

@jeremystretch: Just tested on 2.5.12, and this appears to still be an issue.
https://netbox-dev/api/extras/tags/ still returns as its top-most thing:

{
    "count": 4436,
    "next": "https://netbox-dev/api/extras/tags/?limit=150&offset=150",
    "previous": null,
    "results": [
<SNIP Much Data>

I only have 25 distinct tags (per https://netbox-dev/extras/tags/)
Am I misunderstanding the purpose of the /api/extras/tags endpoint?

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 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

2 participants