Catalog page not showing all components at the first time
gustavolira opened this issue · comments
Describe the bug
Go to the catalog page, by default kind=compnent will be used as default, not all components will be showed at the first time, to see all components you need to change kind=api for example and them select again kind=component
Expected Behavior
Open Catalog page and see all components without need to interact with the page
Versions of software used and environment
RHDH Helm Chart 1.0-190-CI
Platform: OpenShift version4.13.19
@gustavolira Can I ask what you mean by not everything is shown? Is the title of your initial table of components called Owned Components similar to this?
If so, then this is expected since the default is to show all components owned by your backstage identity.
To view all the components, just press the All button in the filters:
This should then show All Components:
Yes it says all=3 but the default filter is for owned components which in your case has 1 component. To view all you just need to select the all filter. You don't need to change the kind filter
@Zaperex I understand, but just change the component to another type and them select kind=component again should keep the same behavior
Oh I think that's because you don't have any owned API entities so it'll then default to all (that's typically the default if you don't own any components for a specific kind of entity). It'll then keep the all filter when you move back to component.
Hi @gustavolira,
This behavior is expected and desired.
Assume your company uses Backstage and the catalog has 10s of thousands of entries in it. You log in to Backstage, go to the catalog page and you will be presented with 10s of thousands of entries. This is not very good UX, since a regular developer is not interested in ALL the components, his attention is focused only on the components he OWNS or he STARRED (aka bookmarked).
In normal cases, guest login wouldn't be even enabled but if it is - Guests don't own any catalog entries. So.. presenting any guest with an empty catalog would be consistent UX, but also wouldn't make much sense... Why present them with an empty screen?
As a result, we have this 2 fold behavior - different for guests where everything is present and focused for logged-in users.
If you don't mind, I'll close this as not a bug. 🙂