[ALOY-1017] Alloy: 'method' and 'module' should not be passed to create a function
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2014-05-19T20:54:39.000+0000 |
| Affected Version/s | Alloy 1.4.0 |
| Fix Version/s | Alloy 1.4.0 |
| Components | n/a |
| Labels | qe-3.3.0, qe-testadded, regression |
| Reporter | Federico Casali |
| Assignee | Tim Poulsen |
| Created | 2014-05-15T22:06:22.000+0000 |
| Updated | 2014-05-20T23:34:49.000+0000 |
Description
Comments
- Tim Poulsen 2014-05-19 It seems to me that this would have little impact on memory use. We're passing in these values as strings, not object references. So, memory consumption should be minimal. Just the same, I've resolved this using the same technique as ALOY-830. Pull request: https://github.com/appcelerator/alloy/pull/402 Test using the Steps to Reproduce described above.
- Ingo Muschenetz 2014-05-19 [~skypanther] Is this to be in Alloy 1.4.0?
- Tim Poulsen 2014-05-20 PR has been cherry-picked to 1_4_X branch
- Federico Casali 2014-05-20 Verified fixed. TiSDK 3.3.0.v20140520141136 Alloy 1.4.0-alpha2 Appcelerator Studio 3.3.0.201405161313 CLI 3.3.0-alpha4 Closing.