Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Why is that so bad? It's pretty convinient. It's tells the user it encountered a error and encourages the user to try again later.
-
But it doesn't tell the debugger how to fix it.
For context's sake, I also added `ERROR 2:` just so I can see which line actually caused it, because there were multiple lines doing that. @HampusMa -
Then it's just to try again later. If it does not work then than the debugger can just contact the developer or google for the fix
-
and if the debugger is the developer? @HampusMa
Can't google a fix if you don't know what went wrong. I guess that's what I'm trying to get across. -
@HampusMa I fear posting there based on other people's experiences. Plus in my case, it was my fault. One of my tables were imported and lost an "AUTO_INCREMENT" field in the registration table.
-
mac-aga20737yIt’s good for the user as the user knows , but bad for the developer as it doesn’t give the slightest clue ,
What could be done is put this as the last default case in the switch case after all the known errors are catched -
When I don't want to say what went wrong exactly I just make up some funny joke related to errors. They are unique and can be traced back by the dev when needed.
-
@Codex404 unlike yours, there were many places in the code that had that line. Error 2 was added by me so I can see where it was triggered from.
-
Nice sending those errors to the client so everyone can see your software infrastructure
-
@LordKerwin well that’s fair enough if you label each error. But again, my frustration is that *I* had to label them because I had to debug ay webapp.
Related Rants
Who ever makes errors like this: FUCK YOU.
rant
errors
php