Closed nichtich closed 5 years ago
We would need different highlight colors for different scenarios:
And combinations of those. The question here is also whether 1. should even be highlighted (#73 originally suggests to remove that highlight).
This also overlaps with #115. It's complicated and I'll move this to milestone 1.0.0.
Depends on #231.
This issue is very related to #343. Here, we are discussing if and how a mapping A->B in Mapping Editor is highlighted in Mapping Browser. But if neither A or B are currently selected, the mapping A->B will not even show up in Mapping Browser, at least not in Mapping Navigator.
Too many kinds of highlighting would be complicated. By now we have:
urn:jskos:mapping:members:
but is currently not)This issue is about adding 3. highlighting if urn:jskos:mapping:content:
id match.
Case 2 and 3 should get same color.
I accidentally implemented it a little bit different now:
urn:jskos:mapping:members:
identifier), the mapping will be highlighted in the same blue color as before.urn:jskos:mapping:members:
), the mapping will be highlighted as well (same color as in (2)).(1) Takes precedence over the others. The difference to your comment is that I've used the members for (3) as well. Is that okay or should we better use the content identifier?
Hover colors should be adjusted depending on the highlight color. After that, this issue can be closed.
If two concepts A and B are selected on the left and on the right, this mapping A to B is also highlighted in the MappingBrowser (and in the OccurrencesBrowser when #73 is implemented).
If the MappingEditor includes two concepts X and Y, it should also be visible whether this mapping exists (MappingBrowser) and what Occurrences of this mapping exist (OccurrencesBrowser). This is tricky because A and B may be equal to X and Y or they may be different.