[TIMOB-23911] Hyperloop: iOS: Improve the way properties are generated
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-10-07T14:16:51.000+0000 |
| Affected Version/s | Release 6.0.0 |
| Fix Version/s | Release 6.0.0, Hyperloop 2.0.0 |
| Components | Hyperloop, iOS, Tooling |
| Labels | qe-6.0.0 |
| Reporter | Eric Wieber |
| Assignee | Jan Vennemann |
| Created | 2016-09-15T18:20:21.000+0000 |
| Updated | 2016-11-11T17:34:06.000+0000 |
Description
As per the discussion in TIMOB-23812 and in https://github.com/appcelerator/hyperloop.next/pull/65
SDK 6.0.0 and Hyperloop 2.0.0 should handle instance properties for UIColor. Ideally, the workaround introduced in the related ticket will be removed and a new API based on properties will be introduced.
https://github.com/appcelerator/hyperloop.next/pull/82
PR merged! Made another PR for the hyperloop-examples repo to be merged when we release 6.0.0 Beta next week: https://github.com/appcelerator/hyperloop-examples/pull/49
Verified fixed, using: MacOS 10.12 (16A323) Studio 4.8.0.201611020954 Ti SDK 6.0.0.v20161109075403 Appc NPM 4.2.8-9 Appc CLI 6.0.0-69 Alloy 1.9.4 Xcode 8.1 (8B62) Hyperloop 2.0.0 Instance properties for UIColor can be used without error. Using the methods to access them will print an error on build that indicates the code should be changed to use the properties.