Hovering over an Object in the Flow should show the Relations menu's information

[Code-Jack]

In the Flow we see nothing more then the Object’s names and their icon.
This is too less information, especially if there are multiple Objects with the same name (it happens sometimes, for different reasons).

The video in this BR shows Objects with the same name and the lack of information:

Converting a Set into a Collection creates Links that lead to other Spaces

What’s The Bug? Converting a Set into a Collection creates Links to user profiles in other Spaces. A click on one of them leads to the other Space. How To Reproduce It You should be member of the Space “Local-first Lovers Club”. Create a new Set in one of your own Spaces (a not shared one, to make things clear). Choose “Object Type None”, but Relation. Choose the Relation “Creation Date”. (The View “All” should now show lots of Objects.) Convert the Set into a Collection. Look in the Flow …

WHAT DO YOU RECOMMEND?

It would be helpful to see more information about an Object in the Flow, without the need to open it.

HOW COULD IT BE DONE?

I suggest a kind of tooltip - an information box that pops up if we hover over an Object in the Flow, that shows everything we normally see in the Relations menu.

• In addition, the Relations menu should also show the Space to that the Object belongs.

REAL WORLD USE CASES

It helps a lot to find different errors in the structure.
For example:

1. Objects with the same name.
   It is very cumbersome to open such identical named Objects one after one only for a short look into them and, after that, navigating back to the Flow and the last position in it to open the next Object.
2. Objects from the wrong type.
3. Object that shouldn’t be there.
4. Object that belong (and lead) to another Space.

RECOMMENDED ALTERNATIVES

–

ADDITIONAL CONTEXT

It would not only be helpful to find self caused errors in the structure, but also for bug hunting and bug reporting to be able to show a bit more information about some Objects in the Flow.

The linked BR is a good example.
The screen recording there shows not only identical named Objects, but also Objects that shouldn’t be there, as well as Objects that lead to another Space.
– Three bugs in one hit!
The additional information could quickly clarify what’s going on without the need to navigate a lot forwards and backwards (and blowing up the screen record to minutes).