Saved objects management table doesn't adhere to the listing limit set in advanced settings

[bhavyarm]

Kibana version: 7.12.0

Elasticsearch version: 7.12.0

Server OS version: darwin

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: If user sets the listing objects limit in advanced settings using "Objects listing limit" - it doesn't reflect in saved objects management table.

Dashboard and visualize work fine.

Steps to reproduce:

1. Set the Objects listing limit in advanced settings as 2
2. Install all the three sample data
3. Go to visualize/dashboard - the listing table displays 2 objects
4. Go to saved objects all of them get displayed

Screenshots (if relevant):
Advanced settings:

Dashboards:

Saved objects:

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[pgayvallet]

Given that the SOM page is an administration page, I'm not sure applying this setting here would really make sense.

I even think it could be potentially dangerous, e.g because of the listingLimit, we're only displaying, say, 5 of 10 dashboards in the table, but then when the customer performs an export by type selecting dashboard, the export will include all 10 of them.

Also, to be honest, I think the initial intent of this setting was to avoid fetching too many objects from the server to the client in a single request, which may be what pages like the dashboard listing page was doing, with a full in-memory load of all the items in their listing table (or is still, I didn't check), but for the SOM page, we're performing one request per page of the table, effectively never loading more than 100 objects at one.

What do the other members think about this?

[lukeelmers]

I think the initial intent of this setting was to avoid fetching too many objects from the server to the client in a single request

Yeah, I tend to agree that it doesn't make a lot of sense to apply this setting to the SO listing page, however I do understand that it's a little confusing from a UX perspective to see more objects than are indicated in the setting, especially when other parts of Kibana adhere to it.

If we did want to apply it to SO listing, we would need to explain the caveats in a big warning at the top similar to what Dashboards have. But at that point, are we really improving the UX, or just making things more confusing? 🙂

This feels like something that @elastic/shared-ux would care about too -- historically we have not applied this setting consistently everywhere.

[pgayvallet]

Closing as working as expected - we're just rightfuly not using this setting in the SOM page