You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing an API endpoint in a web browser, NetBox returns a convenient browsable interface. Currently, this interface includes a button which brings up a modal containing all the filter options for the endpoint. Each field in this form is prepopulated with all potential values. This introduces a huge performance hit when viewing, for example, the IP addresses endpoint, as the interface_id field is pre-populated with all interfaces defined in NetBox.
Given that the available filters for each endpoint are documented separately, there is not much value in including the filter form in the browsable API. We can simply omit it from the API renderer and avoid what is in many cases a large amount of overhead and delay.
The text was updated successfully, but these errors were encountered:
Issue type
[ ] Feature request
[x] Bug report
[ ] Documentation
Environment
Description
When viewing an API endpoint in a web browser, NetBox returns a convenient browsable interface. Currently, this interface includes a button which brings up a modal containing all the filter options for the endpoint. Each field in this form is prepopulated with all potential values. This introduces a huge performance hit when viewing, for example, the IP addresses endpoint, as the
interface_id
field is pre-populated with all interfaces defined in NetBox.Given that the available filters for each endpoint are documented separately, there is not much value in including the filter form in the browsable API. We can simply omit it from the API renderer and avoid what is in many cases a large amount of overhead and delay.
The text was updated successfully, but these errors were encountered: