Skip to content
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

[VariantManagement]: Improper error thrown while trying to rename the variant name #5766

Closed
1 task done
pppwr7 opened this issue Apr 30, 2024 · 0 comments · Fixed by #5798
Closed
1 task done

[VariantManagement]: Improper error thrown while trying to rename the variant name #5766

pppwr7 opened this issue Apr 30, 2024 · 0 comments · Fixed by #5798
Labels
bug Something isn't working

Comments

@pppwr7
Copy link

pppwr7 commented Apr 30, 2024

Describe the bug

In Manage Views Dialog, lets say I change the name of the variant 'Standard1' to 'Standard2' and then back to 'Standard1' , I get the error message 'The view name already exists. Please enter a different name'. I believe, if the name of the variant is changed back to original one, it should not give any error.

Isolated Example

No response

Reproduction steps

  1. open storybook link https://sap.github.io/ui5-webcomponents-react/?path=/story/inputs-variantmanagement--default
  2. open Manage Views dialog.
  3. Change the name of the variant and revert back the change without saving it
  4. Error message is seen

Expected Behaviour

error message should not be shown if the name is same as original one

Screenshots or Videos

image

UI5 Web Components for React Version

1.28.0

UI5 Web Components Version

latest

Browser

Chrome

Operating System

No response

Additional Context

No response

Relevant log output

No response

Organization

No response

Declaration

  • I’m not disclosing any internal or sensitive information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🆕 New
Development

Successfully merging a pull request may close this issue.

1 participant