Patrik Oldsberg

@JounQin thank you! Gonna :shipit:

Quick status update on this one: I've tried out the new flat config in some other places and it was very messy. Considering this very low prio for now

This might be fixed by #25728, or at least provide some more context for the issue

> > Yep I see the benefits on the cookie flow, but it does introduce a lot of complexity 😅. It's a bit extra unfortunate due to the redirect flow...

Thank you for reporting! Just to clarify regarding the reproduction steps: I understand the entity from Azure does not immediately appear in the catalog, but does it appear if you...

@ShiranHi What's missing for me is a design that considers a bit more data. For example, instead of the 4 components kind in the example, what if there are 20?...

@ShiranHi There's an extra complication that I've realized, which is that the available type values depend on what kind you have selected. You can see that in effect on the...

@ShiranHi I gave it a try with the existing filters and I don't love it 😅 I'd say we need a strong indicator that the inability to select multiple kinds...

@ShiranHi both count indicators and clear all exist in the existing multi-select component. This is what the clear all looks like: The count isn't enabled by default afaik, but you...

@ShiranHi the "X" in the component at https://github.com/backstage/backstage/issues/24143#issuecomment-2345970520 is the "clear all" action. I'm thinking at this point the best path forward might be if you have any suggestions for...