-
Notifications
You must be signed in to change notification settings - Fork 707
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.
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
Dashboard/React: "restore defaults" button does not reset BasicDeploymentForm input fields #5025
Comments
The PR for this feature #1277 does show that a "Hostname" field gets reset (We don't see the full form though) |
Thanks for reporting it! We'll take a look to confirm it soon. |
Would be a good start if someone could confirm this behavior or if it is an issue of my browser or kubeapps installation |
@dionysius, I've got some time to have a look at it. I can confirm what you discovered, something is wrong with the update of the input fields. Thanks for reporting it. I have dug into the code and found a workaround, but I haven't checked whether there are unexpected side effects yet. In kubeapps/dashboard/src/components/DeploymentFormBody/BasicDeploymentForm/TextParam.tsx Line 49 in 082be2f
if you replace this It'd be great if you could give it a try, test it and send a PR! Thanks!! |
Describe the bug
When using the "restore defaults" button in a helm chart deployment page the input fields don't get reset. The sliders and checkboxes (at least those who hide other fields) do get reset. The Changes Tab are getting correctly reset though, unsure about the YAML tab - needs checking as well. Same behavior in Brave and Firefox.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The form is reset as if I would refresh the page with Ctrl+R.
Actual behavior
The form is only partly reset. Sliders and checkboxes seem to correctly reset, but all text or password fields keep the input data, while the Changes tab doesn't list any.
Screenshots
Preparation:
After Pressing "Reset defaults":
Desktop (please complete the following information):
Additional context
This problem persists already for a while (6+ months or so), before opening the issue I upgraded kubeapps to latest chart version and I don't know my previous version anymore.
The text was updated successfully, but these errors were encountered: