-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Search Conf Incorrect successful alert message #24352
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@okom3pom LGTM !
Just improve wording.
Co-authored-by: Julie Varisellaz <70583503+Julievrz@users.noreply.github.com>
Co-authored-by: Julie Varisellaz <70583503+Julievrz@users.noreply.github.com>
Hi there ! I think the problem is a bit more complex for this page, because the "Edit alias" can give 3 different results depending on what's modified in the form, and I'm not sure the correct message should always be "Update successful". Ping @PrestaShop/product-team , need some help for this one !
I edit only the "Result" field : In this case, it's indeed only an update of the alias, no new alias is created. For this case, the message is OK.
I edit both "Alias" and "Result" field : In this case, a new alias is created in addition to the original one. IMHO, the message is not OK : It should be "Successful creation". Or the behavior should be modified and the original alias should be replaced by the new one.
I edit only the "Alias" field : In this case, a new alias is created in addition to the original one, but if I edit the same alias again, both aliases are displayed in the "Alias" field. In this case, I'm not sure what should be the message displayed... Both aliases in one edit page : I made a screenrecord of these 3 cases : https://drive.google.com/file/d/1GYGQw6sCNiFH7ZThWw6xRklJxi7yc1Eu/view?usp=sharing Thanks :) |
There is a problem in the behavior as @Robin-Fischer-PS pointed out. In any case, this is an update workflow, so the message is correct even if the actions lead to the creation of a new alias. The behavior is not new, I could reproduce the problem in 1.7.6. So we are not going to adapt the message to a faulty behavior, but we should correct the behavior to match the action and follow the message. |
Thanks @MatShir ! Then this PR is OK : It's QA ✔️ ! Thanks @okom3pom :) |
QA approved, well done! Message to the maintainers: do not forget to milestone it before the merge. |
Thanks @okom3pom @Robin-Fischer-PS |
This change is