[ALOY-759] Support the ability to have compiler conditionals defined as JS constants
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Critical |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2013-07-24T19:37:29.000+0000 |
Affected Version/s | Alloy 1.1.3 |
Fix Version/s | 2013 Sprint 15 |
Components | Runtime, Tooling |
Labels | n/a |
Reporter | Tony Lukasavage |
Assignee | Tony Lukasavage |
Created | 2013-07-24T17:40:26.000+0000 |
Updated | 2013-07-24T19:37:49.000+0000 |
Description
Alloy has a list of platform compiler conditionals that get compiled out of Alloy code depending on the target platform, specified like this:
alloy compile --config platform=ios
In certain situations (like LiveView/TiShadow multiple platform deploys) developers would prefer to leave those values as simply JS constants instead of compiler directives so the same code can be used on multiple platforms. We should investigate being able to run it without the platform config and still have it run successfully.
alloy compile
After investigation, too much of Alloy's compile time process relies on a build platform being present. This is not a feasible option.