Highlight problematic predicate in class detail when navigating from lint issue

[JohnRDOrazio]

Summary

When a user clicks a lint issue (e.g., "Multiple different skos:prefLabel values for language 'no language tag'"), the editor navigates to the affected class. However, there's no visual indication of which predicate/annotation is problematic within that class.

Current Behavior

• Lint issues include details.predicate and details.labels identifying the exact problem
• Clicking an issue navigates to the class in the tree
• The class detail panel shows all annotations, but nothing is highlighted

Desired Behavior

• Clicking a lint issue navigates to the class AND highlights the problematic annotation/predicate
• The highlight could be a colored border, background tint, or badge on the specific annotation row
• Highlight should auto-dismiss after a few seconds or on user interaction

Implementation Notes

• Lint issue details already contain: predicate (e.g. "skos:prefLabel"), language, labels (the conflicting values)
• The ClassDetailPanel annotations section renders each property with its values
• Could pass a highlightAnnotation?: string prop (the predicate URI or curie) via URL query param or state
• The annotations section in ClassDetailPanel.tsx (lines ~826-905) would need conditional styling

Related

• skos:hiddenLabel is missing from backend extraction (ontology.py ANNOTATION_PROPERTIES) — should be added separately

🤖 Generated with Claude Code