Comment #10 on issue 3019 by dsher...@gmail.com: Need a better way to
stringify functions in error messages
http://code.google.com/p/v8/issues/detail?id=3019
Limiting the text to X characters seems like something people should handle
on their own before sending the error message to the server. This is very
easy to implement and I don't think it should be done by chrome at all.
Sometimes developers want to see a very detailed error message that is
above 256 characters... for example, when frameworks like Angular or
Knockout throw an error. Right now if I am about 3 levels deep in the view
model, my error messages get omitted and I have no clue what went wrong.
Also, in the past I have sometimes found seeing the body of the function to
be very useful when trying to figure out what went wrong. I think it would
be a mistake to remove it.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
