[ALOY-395] <Collection> and <Model> generated code should appear BEFORE UI code
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-11-26T22:36:52.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Alloy 0.3.3, 2012 Sprint 24 |
| Components | Runtime, XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-11-15T18:51:25.000+0000 |
| Updated | 2018-03-07T22:26:03.000+0000 |
Description
Right now and tags will only be generated "in time" if they are in the XML before any UI component that needs them. We should make it possible to have these non-UI tags placed anywhere in the code and have them generate in the appropriate spot, before the UI code.
The Alloy.Collection and Alloy.Model parsers can now designate code to be generated before the UI and controller code by attaching it to the returned state as the property **modelCode**