ease.js - Tasks: task #12098, Add option to remove ease.js calls...
You are not allowed to post comments on this tracker with your current authentication level.
task #12098: Add option to remove ease.js calls from stack trace on error
Submitter: | Mike Gerwitz <mikegerwitz> | ||
Submitted: | Sun 10 Jun 2012 03:37:41 AM UTC | ||
Should Start On: | Tue 01 Jan 2013 05:00:00 AM UTC | Should be Finished on: | Mon 01 Apr 2013 04:00:00 AM UTC |
Category: | Core | Priority: | 3 - Low |
Item Group: | Development | Status: | None |
Privacy: | Public | Assigned to: | mikegerwitz |
Percent Complete: | 0% | Open/Closed: | Open |
Planned Release: | None | ||
Keywords: | stack trace, errors |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-bb6a.
Corresponding source code
Whenever ease.js throws an exception, it appears in the stack trace. This can be a bit confusing for developers, as they have to scan downward to see the first line containing their files and have to wonder to themselves in the error was their fault or the fault of ease.js. Furthermore, there are times where ease.js may take up the entire stack trace, depending on the operation being performed (at a default level of 10).
Add an option (whether or not it would be enabled by default is not yet determined) for ease.js to remove itself from the stack trace on error to make the traces more clear.
If an error occurs within ease.js itself, then that will be an exception to this feature. The feature could work by using an Error subtype for all intended exceptions.
Note that this will obviously not be able to remove ease.js from the stack when using a debugger, which may cause certain confusion when debugging, but is important to remain.