Suggestions about Lua Error Reports
Posted: 18 Nov 2024, 18:10
Hello!
Here are my suggestions about Make the Non-Major Lua Error Reports Easier to Check.
First of all, I found that some Lua errors don't cause any crashes, they are just "quiet", I think the reason might be they are not major errors. But it also causes some problems.
My experience:
Sometimes I write some codes for something like a button, but when I click the button(namely execute the code), nothing happens. No crashes, no toasts. And then I have to check the log to get the error report and correct my mistakes. So I think it is necessary to make the Lua error report easier to check. Because usually the lines of the log get really crazy, it will be hard to check.
My suggestions:
Here are my suggestions about Make the Non-Major Lua Error Reports Easier to Check.
First of all, I found that some Lua errors don't cause any crashes, they are just "quiet", I think the reason might be they are not major errors. But it also causes some problems.
My experience:
Sometimes I write some codes for something like a button, but when I click the button(namely execute the code), nothing happens. No crashes, no toasts. And then I have to check the log to get the error report and correct my mistakes. So I think it is necessary to make the Lua error report easier to check. Because usually the lines of the log get really crazy, it will be hard to check.
My suggestions:
- Move the Non-Major Lua Error Reports to crash.txt or error.log.
- I think it is also nice to make a new .txt or .log file for the Lua Error Reports.
Hi, Just anyone nice too meet you