Fixes #4004

[sumitkukrejas]

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

What changes did you make? (Give an overview)

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]

Hello there sumitkukrejas! 👋

Thank you and congrats 🎉 for opening your first PR on this project! ✨ 💖

We will try to review it soon!

[Haarolean]

Hey @sumitkukrejas, thanks for a contribution! Unfortunately, this repo is not maintained (source), but we'll happy to see your contributions here: https://github.com/kafbat/kafka-ui

[Fe1777]

Certainly! Here is a structured GitHub issue description for the PR #4433 in the Kafka-UI repository that addresses issue #4004.

---

Title: Fix for Issue #4004

Type: Bug Fix

Reported by: sumitkukrejas

---

Description

This PR fixes the issue described in #4004. The changes made are crucial to ensure the proper functioning of the affected component in the Kafka-UI.

Breaking Change

If this PR introduces a breaking change, please describe the impact and migration path for existing application instances:

• Impact: [Provide detailed description of the breaking change]
• Migration Path: [Provide a clear, step-by-step migration path for existing applications, if applicable]

Changes Made

An overview of the changes made to address the issue:

• [Summary of changes]

Review Focus

Points that reviewers should focus on:

• [Specific areas or parts of the code that need careful review]

Testing

Please indicate how this has been tested, put an "x" (case-sensitive!) next to all that apply:

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

Checklist

Ensure the following items are checked; otherwise, the build will fail. Put an "x" (case-sensitive!) next to all the items:

• 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

Contribution Guidelines

Make sure to check out the Contributing and Code of Conduct guidelines.

A Cute Animal Picture

(Not mandatory but encouraged)

---

Related Issues/PRs

• Related Issue: Issue #4004
• Related PR: PR #4433

Thank you!

Thank you for your contribution to fixing this issue in Kafka-UI. Your efforts help in enhancing the stability and usability of the project.

---

Feel free to adjust the template as needed to align with any additional context or specifics of the pull request and related issues.