if(response.Success == false);
{
Success = false;
AddSystemException($"{LibraryID}.{FunctionID}", "Rest Request Error", null);
try { listErrors.AddRange(JsonConvert.DeserializeObject<List<(string, string, string, object)>>(response.errorJson)); } catch {}
return;
}
Spot the mistake that kept me up for 3 extra hours.
Not knowing when to call it a day
Only took me a glance. Shoulda called me
That one will get you every time;
Oh my! I was about to ask someone to give us the answer for the non-coders. Then I looked at it and saw it right away. Those are the errors that get me all the time.
Well, that’s why …
If you’re going to make a mistake, don’t half-
it.
End of statement.
One of the things I remember to this day was my Jazz band teacher in high school told us. “If you play a wrong note, just play in like it’s on purpose, people usually only know you made a mistake if you act like you made a mistake. And with Jazz, just a move a half a note either way, and you’re back to being right”
One of those little things you remember for the rest of your life.
damn black magic
i have no shame using chatgpt to check my work. I dont code enough to be a super hero. =/
Theres a local ai called LM Studio that i used for anything business specific so i dont have to give any info to chatgpt, but its not as f
There’s another mistake…
Never catch { } unless you have a good reason to…
Nope
I do.
This is a logging function, I absolutely do not want any errors whatsoever to halt, and I don’t want to do anything with them. (At least at the moment.)
I’ll probably catch them at some point later for a failover log, but not now.
I haven’t read the replies yet. I’m guessing it’s your semicolon in the first line?
