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

improved messaging on showing admin-ui errors #2416

Open
HoseinGhanbari opened this issue Sep 28, 2023 · 1 comment
Open

improved messaging on showing admin-ui errors #2416

HoseinGhanbari opened this issue Sep 28, 2023 · 1 comment

Comments

@HoseinGhanbari
Copy link
Contributor

Is your feature request related to a problem? Please describe.
there are cases when you are using some zone elsewhere in the system as a relationship and when you try to delete the base zone, admin-api generates something like this The selected Zone cannot be deleted as it is used in the following TaxRates but the end user cannot see any message. that message is what shown inside browser's network inspect. in this scenario shop manager don't know what to do because there is no feedback to say removal failed, you should first remove the dependent data. also note that this is not only for zone entity, i saw this behavior in some other relational entities as well.

Describe the solution you'd like
if we could show the end user of admin-ui that something went wrong and help them fix the issue they can fix themselves would be really nice.

Describe alternatives you've considered
any kind of improvement on messaging system and alerts would be nice, specifically on foreign key checks / entity relationship which prevents data removal due to a known/logical reason.

Additional context
currently there is no additional context required to describe the improvement.

@dlhck
Copy link
Collaborator

dlhck commented Sep 27, 2024

Should be done together with #2903

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants