Can some business logic error messages in the model not be output?

For example, if I modify a product, the product image is designed to delete the original one first and then add the new one. If there is an error in deleting the previous image, then I will directly output "Is there an error in deleting the previous image?" Is this an error message? Only for testing phase? ? ? Do users still encounter this kind of problem when using it

Reply content:

For example, if I modify a product, the product image is designed to delete the original one first and then add the new one. If there is an error in deleting the previous image, then I will directly output "Is there an error in deleting the previous image?" Is this an error message? Only for testing phase? ? ? Do users still encounter this kind of problem when using it

All situations are possible, and users may also encounter this situation.
User experience must be good. For example, as a user of your website, I want to update my products now, but something went wrong while updating the pictures. You didn’t give any prompt, so I naturally thought that I had updated successfully. But after a few days, I looked and found that I The products still have old pictures. Then at this time, I will feel that the user experience of your website is not good. If the user experience is not good, as long as there is a website of the same type as yours on the market, I may try it, but you may lose traffic.

So, whether to mention or not is related to user experience. A good experience requires reporting conditions to users, but at the same time, there is no need to report too detailed conditions. For example, you can just say that the image upload failed. If you also report the path of the failure and what code caused it, this would be a bit redundant.

Some output-sensitive output that users cannot understand should not be shown to users. The user experience is not good.
Users don’t care how fault-tolerant your website system is, they just depend on whether the functions they want are implemented. A simple reminder is fine, for example: the system is busy, please try again later, or the network condition is not good, etc.