[TIMOB-11939] CodeProcessor: Unknown/Ambiguous reporter plugin/visualizer
| GitHub Issue | n/a |
|---|---|
| Type | Sub-task |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-12-07T23:44:39.000+0000 |
| Affected Version/s | Release 3.0.0 |
| Fix Version/s | Release 3.0.1, Release 3.1.0, 2012 Sprint 25, 2012 Sprint 25 JS |
| Components | Code Processor |
| Labels | n/a |
| Reporter | Bryan Hughes |
| Assignee | Praveen Innamuri |
| Created | 2012-12-03T17:53:34.000+0000 |
| Updated | 2017-03-09T00:38:49.000+0000 |
Description
When trying to determine why a piece of code was not analyzed, it is almost always necessary to see if we are in an ambiguous context/block and if values are unknown. Currently, one must debug the code processor itself to determine this information. We should create some way of reporting this information via a plugin. Simply dumping to the screen may be information overload though, so we should consider alternative ways of reporting this information, such as writing the source code to file with some sort of annotation.
Upped the time estimate because uglify's endline/column markers are broken and I now have to write my own AST serializer. It's not a bad thing though because it's something we will need later anyways.
Closing ticket as fixed.