[TIMOB-13676] Code Processor: Rework module specification in configuration files
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-05-03T17:20:57.000+0000 |
| Affected Version/s | Release 3.1.0 |
| Fix Version/s | 2013 Sprint 09 JS, 2013 Sprint 09, Release 3.1.1, Release 3.2.0 |
| Components | Code Processor |
| Labels | n/a |
| Reporter | Ingo Muschenetz |
| Assignee | Matt Langston |
| Created | 2013-04-26T00:47:50.000+0000 |
| Updated | 2017-03-14T20:45:16.000+0000 |
Description
For consistency and future expandability, the code processor should accept the path to a module instead of the path to the js file for commonjs modules and an empty string to for native modules.
PR: https://github.com/appcelerator/titanium-code-processor/pull/168 1_0_X PR: https://github.com/appcelerator/titanium-code-processor/pull/169
Is there a way we can check this?
If the dependent studio fix is actually fixed, than so is this. This change was purely a studio interface refactoring. Sorry, it should have been a task, not a bug.
Closing ticket as fixed.