[TIMOB-13879] Code Processor: Rework how source maps are specified in config files
GitHub Issue | n/a |
---|---|
Type | Story |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2013-05-17T01:16:02.000+0000 |
Affected Version/s | Release 3.1.1 |
Fix Version/s | 2013 Sprint 10 JS, 2013 Sprint 10, Release 3.1.1, Release 3.2.0 |
Components | Code Processor |
Labels | n/a |
Reporter | Ingo Muschenetz |
Assignee | Matt Langston |
Created | 2013-05-16T08:03:48.000+0000 |
Updated | 2017-03-09T18:12:25.000+0000 |
Description
The current way that source maps are defined is cumbersome and error-prone to work with. Instead of specifying each map, only the source map directory should be specified, and the code processor should be the one to crawl the directory since it has to load the maps anyways.
PR: https://github.com/appcelerator/titanium-code-processor/pull/190 1_0_X PR: https://github.com/appcelerator/titanium-code-processor/pull/191
To test: Run against an alloy map and make sure that lines are being source mapped (when possible). There should be no behavioral change between this PR and master (all changes are under the hood).
Closing ticket as fixed.