KC: Show connector-level trace when status is FAILED

[mehmetcangulesci]

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Implemented the feature request #1318
Fixes #1318

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[github-actions]

Hi mehmetcangulesci! 👋

Welcome, and thank you for opening your first PR in the repo!

Please wait for triaging by our maintainers.

Please take a look at our contributing guide.

[Leshe4ka]

Hi, @mehmetcangulesci !
Thank you for contributing! I have add few comments, please, check it out

[mehmetcangulesci]

Hi, @mehmetcangulesci ! Thank you for contributing! I have add few comments, please, check it out

Hi @Leshe4ka Thank you for the detailed review and great suggestions!

I've implemented all your feedback:

✅ Reusable Modal Component: Created a reusable Modal component in components/common/Modal that can be used throughout the application
✅ Helper Function: Refactored the conditional logic into a canShowTrace helper function with proper TypeScript typing
✅ Clickable Prop: Added a clickable prop to the C.Tag component to replace inline styles
✅ Conditional Rendering: Fixed the conditional rendering to avoid empty wrapper elements

[Haarolean]

@mehmetcangulesci thank you for your contribution. For the future reference, please do not raise PRs before the issue has been triaged and OK'ed. This feature is nice, but it might happen that we might not want to accept everything proposed even with a submitted PRs.

[Haarolean]

@mehmetcangulesci could you please address failing backend build? From a quick look, this might be related to the fact you've adjusted .tsp spec which is used for the frontend files generation, but the origin is OpenAPI reference (contract/src/main/resources/swagger/kafbat-ui-api.yaml).

[mehmetcangulesci]

@mehmetcangulesci thank you for your contribution. For the future reference, please do not raise PRs before the issue has been triaged and OK'ed. This feature is nice, but it might happen that we might not want to accept everything proposed even with a submitted PRs.

@Haarolean Thanks for the feedback! Totally understood — I’ll make sure to wait for issue triage and approval before opening a PR next time. Appreciate the clarification and the review 🙏

[mehmetcangulesci]

@mehmetcangulesci could you please address failing backend build? From a quick look, this might be related to the fact you've adjusted .tsp spec which is used for the frontend files generation, but the origin is OpenAPI reference (contract/src/main/resources/swagger/kafbat-ui-api.yaml).

@Haarolean Thanks for catching that! I’ve fixed the failing backend build in the latest commit.

[Haarolean]

@mehmetcangulesci thanks. Please also refrain from force pushing next time, as it renders the diff as a new one which forces the reviewers to review the whole PR again.

[mehmetcangulesci]

@mehmetcangulesci thanks. Please also refrain from force pushing next time, as it renders the diff as a new one which forces the reviewers to review the whole PR again.

@Haarolean Thanks for the heads-up! Got it, I’ll avoid force pushing next time to keep the diff reviewable.

[Haarolean]

@mehmetcangulesci thanks for your first contribution to kafbat ui!