-
Notifications
You must be signed in to change notification settings - Fork 29
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
Forward to list on missing object during deletion #270
Conversation
I'm 👍 for this, an Exception is too harsh in this case. |
@@ -70,6 +70,7 @@ action.object.delete: | |||
confirm: Etes-vous sur de vouloir supprimer cet élement? | |||
success: L'élément sélectionné a été supprimé. | |||
error: L'élément sélectionné ne peut pas être supprimé. | |||
notfound: Element ne peut pas être supprimé car il est déjà supprimé. |
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.
French one: Suppression impossible : l'élément est inconnu
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.
Done.
2 comments, otherwise : 👍 |
👍 good for me |
Forward to list on missing object during deletion
When a object is not found during deletion (for example, when clicking the confirm button twice on the confirm page), you get an Exception which is too general: Object could not be removed.
This PR introduces an automatic forward, which creates a notification that it could not be removed as it already was removed.
Also added some tweaks in parts of the code to make it more consistent.