Replies: 1 comment 4 replies
|
The initial things that came into my head is to let the client know what's wrong.... so for example in the demo if the verse doesn't exist nothing is shown, but it should probably show a message saying that this verse does not exist.... |
|
I don't know if you saw, but on mCart we had MAlerts in the components. It's a lightweight component I created based on bootstrap, and it's job is to give alerts. You can set the status like |
|
The only difference with MAlert from Bootstrap's built-in alert is that it just fades in. |
|
And I think that most of the handling should be done on the client side to minimize server load, because nodejs is single threaded by nature (although it is concurrent) so this would be a design so as to not hurt server performance. |
|
@j-koziel what do you actually mean by error handling I.e. do you mean in the frontend, API, or all around? |
Uh oh!
There was an error while loading. Please reload this page.
Let me know what ideas you might have for this and I'll try my best to contribute with the ✨ expertise ✨ that I have.
All reactions