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
Hey! I've noticed that the TpError message can often be difficult to work with, and often doesn't tell me which input is causing the error which makes debugging more difficult.
A few ways I think it could be improved:
Printing the object causing the error to the console. A console.error({ controller }) would go very far. If not that, then even the name or any other identifying information would help a lot.
Dumping the stack in its own log so it's easier to work with.
Not sure how it would look exactly, but something like:
As it is now, it can be cumbersome to navigate the stack trace as a string in devtools, and things like links obviously don't work. It would be nice to have the objects in the console instead of stringified versions from TpError:
These are just some ideas -- what do you think? I'd be happy to make a PR if you like any of them!
The text was updated successfully, but these errors were encountered:
Hey! I've noticed that the
TpError
message can often be difficult to work with, and often doesn't tell me which input is causing the error which makes debugging more difficult.A few ways I think it could be improved:
Printing the object causing the error to the console. A
console.error({ controller })
would go very far. If not that, then even thename
or any other identifying information would help a lot.Dumping the stack in its own log so it's easier to work with.
Not sure how it would look exactly, but something like:
As it is now, it can be cumbersome to navigate the stack trace as a string in devtools, and things like links obviously don't work. It would be nice to have the objects in the console instead of stringified versions from
TpError
:These are just some ideas -- what do you think? I'd be happy to make a PR if you like any of them!
The text was updated successfully, but these errors were encountered: