[ALOY-253] Investigate improving uglifyjs "beautify" output
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-09-27T21:19:59.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2012 Sprint 20, Release 3.0.0 |
| Components | Runtime, XML |
| Labels | notable |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-09-12T10:50:45.000+0000 |
| Updated | 2018-03-07T22:25:54.000+0000 |
Description
Since true debugging will need to wait a bit, let's see if we can improve the output from uglifyjs to make it a bit more readable.
Did more testing, all looks good. This output is probably as good as we are going to get without source mapping alloy code to the generated code. It should allow developers using the runtime debugger to more meaningful step through an application than before when the more intrusive mangling and compression settings were used.