Don't persist page size preference across views

[jeremystretch]

NetBox version

v3.4.5

Feature type

Change to existing functionality

Proposed functionality

When viewing a list of objects in the NetBox UI, the user can select a page size to determine how many objects to render in one view. (Default options range between 25 and 1000 objects.) Once a page size has been selected, it will persist as the user navigates to other areas of the application. This FR proposes removing the persistence, so that navigating to a different object view returns the default page size.

Use case

We've found that users will often increase the page size while viewing one type of object for a specific purpose, without realizing as they navigate elsewhere in NetBox that the page size has remained in effect. This can lead to frustration stemming from unnecessarily long load times as many more objects than required are being fetched.

Database changes

No response

External dependencies

No response

[jsenecal]

Would persistence follow the page size preference of the individual user ?

[jeremystretch]

@jsenecal are you referring to the "page length" user preference?

I think we'd still allow a user to set their global preference this way; we just wouldn't update it automatically when specifying a page size under a specific table.

[jsenecal]

Yes, this is what I had in mind. The behavior you described works for me. I would change the description to The default number of objects to display per page however.