[ALOY-1633] Alloy should assign globals directly rather than using the implicit global scope of app.js
GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2019-11-21T14:01:03.000+0000 |
Affected Version/s | Alloy 1.13.1, Alloy 1.13.2 |
Fix Version/s | CLI Release 7.1.2 |
Components | Runtime |
Labels | engTriage |
Reporter | Ewan Harris |
Assignee | Ewan Harris |
Created | 2018-09-27T15:53:29.000+0000 |
Updated | 2019-11-21T14:01:03.000+0000 |
Description
Description
Alloy currently makes use of the implicit global scope of the app.js file to make the Alloy, _, and Backbone variables globals. Alloy should assign these to the global scope directly.
When doing this we should be sure to replicate the exact behaviour of the existing code, so make sure that they stay overwritable etc.
Comments
JSON Source
PR: https://github.com/appcelerator/alloy/pull/911
When disabling the global-scope plugin KS-v2 errors on start up due to the following error (global-scope plugin is due for removal in SDK 9):
Fixed in https://github.com/appcelerator/alloy/commit/e638e557f87eab01bea8bd39c5afd64fcdcfb36c, new Alloy release going through Jenkins atm. Should be in a preprod CLI in ~1 hour
Closing ticket, fix verified in CLI version
{"NPM":"4.2.15-1","CLI":"7.1.2-master.9"}
. Tested using the KS-V2 app and disabling the global scope.