UX: Erroneous "unlinked" when all concepts are definitions

[joeflack4]

Overview

When 100% of the concepts in an expansion are also definitions, VS Hub erroneously thinks that they are unlinked, and inserts an "unlinked" root above them.

Replication

1. Go here: https://purple-plant-0f4023d0f.2.azurestaticapps.net/cset-comparison?codeset_ids=479356
2. Observe that all of the concepts are definitions, yet they show up as unlinked.

[Sigfried]

It's just hanging when I go to that url right now.

[Sigfried]

Still waiting for 7ba38f7 to deploy, but with http://localhost:3000/cset-comparison?codeset_ids=479356, I see

which looks ok to me. It doesn't matter that they are definition concepts, they are still not linked to each other, so the are appearing where they belong. Maybe if all concepts are unlinked, they don't need to be grouped under an unlinked node, but it's not a high priority.

@joeflack4, if I'm misunderstanding, please explain and reopen.

[joeflack4]

Maybe if all concepts are unlinked, they don't need to be grouped under an unlinked node, but it's not a high priority.

That's just it. I feel like if they are definition concepts they shouldn't appear there, but at the root.

Let's leave it open. But I'll rename it. It's not a bug, it's a design decision. If we ever are able to work on this again, we can ask what others prefer.