You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are close to 1000 errors in the database
I checked and these errors don't look so much helpful
Also, Heroku has a limit of 10.000 rows of free
So we should try to think of a way to save useful errors to debug, saving rows on Heroku, and having always useful logs to check when a user in production has some error. Also, we want that the solution was not exhaustive how to write manually the line of code of the error.
The text was updated successfully, but these errors were encountered:
I think that something interesting to save is the stack_trace, if we create a new Error in the catch statement, for example:
We could see at the stack trace the function name and the line of code:
But in production, as the code is formatted by webpack to save space and browser compatibility, the stack trace is not showing the line of code exact, and the name of the file and function is hidden between a lot of text.
I don't found any way to get a more clean Stack trace in Javascript.
The only thing that I found is the Custom Errors that could help a little but not all ;( Here's the best article that I found about custom errors and error handling: https://javascript.info/custom-errors . But that won't cover complete our requirements.
Currently, there are close to 1000 errors in the database
I checked and these errors don't look so much helpful
Also, Heroku has a limit of 10.000 rows of free
So we should try to think of a way to save useful errors to debug, saving rows on Heroku, and having always useful logs to check when a user in production has some error. Also, we want that the solution was not exhaustive how to write manually the line of code of the error.
The text was updated successfully, but these errors were encountered: