@antoniokov, I just now noticed that the breadcrumbs are also showing up in the collections areas where you select from just the relation in those collections. I think this is particularly redundant since by definition, the only results that can be seen are from the linked DB of the relation. You can’t see in those areas any views or docs, which are types of Fibery “items” that can benefit from having a breadcrumb about their location. So again, my point here is that with the breadcrumb, you now have 1/2 of the real estate you had before taking up by a breadcrumb that is not giving any useful information here in the collections area. Would you guys consider giving some thought to limiting the breadcrumb to the global search, where it has much better utility than in collections?
I will also note that maybe you could unify some stuff here between global search and the search in Collections, since you DO have the ability to see grayed out closed entities in the collections areas that we are discussing here. It just seems inconsistent, because it would appear to my eye, and I’m guessing many others’, that these two implementations of search are very similar since you added in breadcrumbs in both with one release, but you can’t get the grayed out closed entities into the global search, which is a highly discussed need here in the community.
Thanks for listening!