Skip to content

Brokers: Configs - The list isn't reset to the default state after the search #4179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
4 tasks done
vpopova294 opened this issue Aug 31, 2023 · 5 comments · May be fixed by #4261
Open
4 tasks done

Brokers: Configs - The list isn't reset to the default state after the search #4179

vpopova294 opened this issue Aug 31, 2023 · 5 comments · May be fixed by #4261
Labels
good first issue Up for grabs scope/frontend status/accepted An issue which has passed triage and has been accepted status/confirmed A bug which actuality is confirmed type/bug Something isn't working

Comments

@vpopova294
Copy link

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Relevant results based on key word in Search input are still kept.

Expected behavior

  • the list of configs isn't reset to the default state;
  • all available records should be displayed.

Your installation details

Running master-labeled docker image

Steps to reproduce

  1. Login to Kafka-UI
  2. Navigate to Brokers
  3. Click on the broker and switch to Configs tab.
  4. Search by "false" value
  5. Click on the cross (X)

Screenshots

reset.to.default.state.mp4

Logs

No response

Additional context

No response
@vpopova294 vpopova294 added type/bug Something isn't working status/triage Issues pending maintainers triage labels Aug 31, 2023
@github-actions
Copy link

Hello there vpopova294! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

@Haarolean Haarolean added good first issue Up for grabs scope/frontend status/accepted An issue which has passed triage and has been accepted status/confirmed A bug which actuality is confirmed and removed status/triage Issues pending maintainers triage labels Sep 11, 2023
@rahmatrmdn
Copy link

rahmatrmdn commented Sep 24, 2023 •
edited
Loading

Hello @Haarolean I'm a beginner in contributing open source project. I make my first pull request to fix this issue. Please review my PS. Thank in advice!

#4261

@rahmatrmdn rahmatrmdn linked a pull request Sep 24, 2023 that will close this issue
Open
13 tasks
@Haarolean
Copy link
Contributor

@rahmatrmdn #4255
I don't have r/w permissions at the moment so can't do anything about your PR

@Haarolean Haarolean mentioned this issue Feb 5, 2024
Closed
@vikasrajputin
Copy link
Contributor

Hello @Haarolean

Is this issue still open, if yes I would like to work on it.

@Haarolean
Copy link
Contributor

@vikasrajputin #4255 -> https://github.com/kafbat/kafka-ui

@github-project-automation github-project-automation bot moved this to One shots in Up for grabs Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Up for grabs scope/frontend status/accepted An issue which has passed triage and has been accepted status/confirmed A bug which actuality is confirmed type/bug Something isn't working
Projects
Up for grabs
Status: One shots
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FE: Trigger onChange in clearSearchValue on Search component rahmatrmdn/kafka-ui
4 participants
@Haarolean @vikasrajputin @rahmatrmdn @vpopova294