Deprecated filesystem APIs

[peterflynn]

This extension uses APIs which are deprecated as of Brackets Sprint 34 (the next release):

• NativeFileSystem.FileEntry
• DirectoryEntry.getFile() (without create flag)
• DirectoryEntry.createReader()

These APIs should continue to work for now (though please test your extension to be sure!). However, the deprecated APIs will be removed around the end of this year, so you should migrate away from them soon.

It should be fairly straightforward to migrate to the new APIs. (And if you release an updated extension requiring the new APIs, users of earlier Brackets versions will still be able to install the older release of your extension that is compatible with their build).

See this discussion thread for more background on the API changes.

[peterflynn]

I also noticed the extension contains this code: FileUtils.showFileOpenError(error.code, filePath). I think this was broken even before the API changes mentioned above (there used to be an error.name field, but I don't think there was ever an error.code). Starting in Brackets Sprint 34 however, the errors are just string constants. So to be compatible with all recent versions of Brackets, you could use this code: FileUtils.showFileOpenError(error.name || error, filePath)

[le717]

@davidderaedt The long-deprecated Brackets NativeFileSystem module reported here will be removed in the very near future, possibly in 1.1. You will need to update your extension on order to preserve future Brackets compatibility.

See adobe/brackets#6127 and adobe/brackets#8751.