Re: [w3c/filesystem-api] Is this spec deprecated? (#8)

Now I'm confused 

File API (Directories and System): Edge and firefox have recently included a subset of this
FileSystem API (this repo): Is this new api?

I see two main difference in this two api's that this is being promisified :+1:
and that this API don't seems to support having a file and a directory with the same name :-1:

> > [createFile](http://w3c.github.io/filesystem-api/#widl-Directory-createFile-Promise-File--DOMString-path-CreateFileOptions-options)
When the createFile(path, options) method is run, the user agents must run the steps below:
        3 If the nth token in tokens identifies a directory, reject p with an InvalidStateError.

> and where `get` is a combination of both `getFile` and `getDirectory`

> > [get](http://w3c.github.io/filesystem-api/#widl-Directory-get-Promise--File-or-Directory---DOMString-path)
        2.2.1 If d is a file, resolve p with a new File representing d.
        2.2.2 If d is a directory, resolve p with a new Directory representing d.

How else are you going to copy a folder from the server or users OS if there can't be a folder & file with a same name? Blink's sandboxed filesystem, and most other OS supports it but this don't

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/filesystem-api/issues/8#issuecomment-255462955