[TIMOB-9465] TiAPI: Geolocation.hasCompass function vs property
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2017-06-15T17:51:21.000+0000 |
| Affected Version/s | Release 2.1.0 |
| Fix Version/s | n/a |
| Components | TiAPI |
| Labels | api, parity |
| Reporter | Josh Roesslein |
| Assignee | Eric Merriman |
| Created | 2012-06-08T09:49:34.000+0000 |
| Updated | 2017-06-15T17:51:21.000+0000 |
Description
Android and iOS have an API for accessing the device's compass.
Since not all devices have a hardware compass, you must test for its existence.
Android implements this as a getter property called "hasCompass".
Android also provides a function called "getHasCompass".
iOS implements this as a method called "hasCompass".
This creates an unnecessary parity difference. We should determine if this property
should be changed on one of the platforms to be either a function or getter property.
We could also introduce a new property/function to avoid breaking changes to this API.
Closing ticket due to time passed and lack of progress in the past few years. Any problems, please file a new ticket.