Add 'brief' and 'exclude' to Swagger Documentation #3469

Closed
opened 2025-12-29 18:29:23 +01:00 by adam · 5 comments
Owner

Originally created by @dstarner on GitHub (Mar 12, 2020).

Change Type

[X] Addition
[ ] Correction
[ ] Deprecation
[ ] Cleanup (formatting, typos, etc.)

Area

[ ] Installation instructions
[ ] Configuration parameters
[ ] Functionality/features
[X] REST API
[ ] Administration/development
[ ] Other

Proposed Changes

Add the brief and exclude parameters to the Swagger API for appropriate routes such as list devices and get device so that they can be used by Swagger clients. They should be included in the same manner that the q parameter is.

Originally created by @dstarner on GitHub (Mar 12, 2020). ### Change Type [X] Addition [ ] Correction [ ] Deprecation [ ] Cleanup (formatting, typos, etc.) ### Area [ ] Installation instructions [ ] Configuration parameters [ ] Functionality/features [X] REST API [ ] Administration/development [ ] Other <!-- Describe the proposed change(s). --> ### Proposed Changes Add the `brief` and `exclude` parameters to the Swagger API for appropriate routes such as list devices and get device so that they can be used by Swagger clients. They should be included in the same manner that the `q` parameter is.
adam added the pending closure label 2025-12-29 18:29:23 +01:00
adam closed this issue 2025-12-29 18:29:23 +01:00
Author
Owner

@kobayashi commented on GitHub (Mar 16, 2020):

Is this the same as #4357?

@kobayashi commented on GitHub (Mar 16, 2020): Is this the same as #4357?
Author
Owner

@dstarner commented on GitHub (Mar 16, 2020):

No, this is to add documentation on it, since neither variables are present in the Swagger documentation

@dstarner commented on GitHub (Mar 16, 2020): No, this is to add documentation on it, since neither variables are present in the Swagger documentation
Author
Owner

@dstarner commented on GitHub (Mar 17, 2020):

@kobayashi / @jeremystretch is this something that can be approved so that I can create a PR for it?

@dstarner commented on GitHub (Mar 17, 2020): @kobayashi / @jeremystretch is this something that can be approved so that I can create a PR for it?
Author
Owner

@stale[bot] commented on GitHub (Mar 31, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Mar 31, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@stale[bot] commented on GitHub (Apr 8, 2020):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Apr 8, 2020): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3469