[TIMOB-6932] iOS: Incorrect deprecation of Ti.Filesystem.File.writable
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-01-23T16:14:16.000+0000 |
| Affected Version/s | Release 1.8.0.1 |
| Fix Version/s | Sprint 2012-01, Release 2.0.0, Release 1.8.1 |
| Components | iOS |
| Labels | module_filesystem, parity, qe-testadded |
| Reporter | Arthur Evans |
| Assignee | Blain Hamon |
| Created | 2011-12-29T15:31:29.000+0000 |
| Updated | 2012-02-02T13:59:16.000+0000 |
Description
According to the Filesystem parity spec:
https://wiki.appcelerator.org/display/spe/Filesystem+Behavior+Parity
The "writeable" property is supposed to be deprecated in favor of writable.
However, in the iOS code, the writable property returns a deprecation warning and points users to "writeable"--just the opposite of the spec.
Android only supports writable. Propose we change the iOS code--or else update the spec and Android code to match.
For KS filesystem.js on 1.8.0.1: Android returns: * writeable property: undefined * writable property: false * writeable method: exception - no method * writable method: exception - no method iOS returns: * writeable property: true * writable property: true * writeable method: exception * writable method: exception
Closing issue Tested with Ti Studio 1.9.0.v20120111233134 Ti Mob SDK 1.8.0.1 OSX Lion iPhone Sim Expected behavior of writeable showing proper deprecation warning is shown
Reopening and closing this issue to update label and Fix Version field.
updated labels