-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] NativeFileError for error callbacks in NativeFileSystem (#2057) #2217
Comments
Comment by jasonsanjose Initial review complete. What were the 3 extensions that use |
Comment by jbalsas I've updated the name and its references and pushed the changes. The three extensions I've identified are:
|
Comment by jasonsanjose
|
Comment by jbalsas Done! ;) |
Comment by jasonsanjose Confirmed unit tests are passing on mac. Merging. |
Comment by jasonsanjose
|
Issue by jbalsas
Sunday Dec 09, 2012 at 20:21 GMT
Originally opened as adobe/brackets#2318
This is a possible fix for #2057. It introduces a new
NativeFileError
implementingDOMError
to substitute the currentFileError
as the specs dictate.Important changes
FileError
polyfillNativeFileSystem.FileError
is moved to its own moduleNativeFileError
. I thougth it would make more sense, and avoids dependencies withNativeFileSystem
when only wanting to check error name values._nativeToFileError
has been modified to just convert a brackets.fs error code to a NativeFileError error name. Hopefully this clears out any confusion in NativeFileSystem by making explicit all the error constructors in the same way.DOMError
has aname
attribute whereFileError
hadcode
.Notes
FileError
, nor the need to use a polyfill for the in-browser branch.DOMError
andFileError
may break error handling in existing extensions. We could add acode
attribute in ourNativeFileError
class to ensure backward compatibility. I've done a quick search though, and only three extensions seem to be using error.code right now.jbalsas included the following code: https://github.com/adobe/brackets/pull/2318/commits
The text was updated successfully, but these errors were encountered: