UX: Erroneous "unlinked" when all concepts are definitions
Opened this issue · 6 comments
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
- Go here: https://purple-plant-0f4023d0f.2.azurestaticapps.net/cset-comparison?codeset_ids=479356
- Observe that all of the concepts are definitions, yet they show up as unlinked.
It's just hanging when I go to that url right now.
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.
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.
There's actually no way for a concept to appear as unlinked unless it's a definition -- or included through Add Concepts.
That's what I'm thinking the main use case is; add concepts.
I think that's the only time I've ever really noticed it.
Maybe we just need a better term. Unlinked doesn't mean it's not linked to the concept set; it means it's not linked to any other concepts in the hierarchy.