Update issues table to use LabelLists instead of custom labels#3816
Update issues table to use LabelLists instead of custom labels#3816
Conversation
Summary by CodeRabbit
WalkthroughReplaces inline per-label rendering in IssuesTable with a LabelList component and updates unit tests to mock and assert LabelList props (entityKey, labels, maxVisible), ensuring previous maxVisibleLabels behavior is preserved. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3816 +/- ##
==========================================
- Coverage 90.24% 90.23% -0.02%
==========================================
Files 463 463
Lines 14410 14411 +1
Branches 1936 1936
==========================================
- Hits 13005 13004 -1
- Misses 987 988 +1
- Partials 418 419 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
a1826b8
|



Updated Mentorship portal Issues table to use existing
LabelListcomponent instead of generic labelsChecklist
make check-testlocally: all warnings addressed, tests passed