browser-fs-access icon indicating copy to clipboard operation
browser-fs-access copied to clipboard

Describe differences to directly working with the File System Access API in README

Open thien-do opened this issue 2 years ago • 3 comments

Hi :D If you're ok, I'd like to have a small PR to add a small section to the README regarding the migration from the native file system.

Thing is, I used the native file system first, then as my app needs to go live, I adopt this library, and there are several things I learned that I think would be useful for others in similar situation.

For example:

  • In the native API, the main model is "handle", and you get the file content from there, async
  • In this API, the main model is the file itself, and the "handle" is an optional object
  • Stuff like persisting to local storage (indexed DB actually)

thien-do avatar Sep 25 '21 14:09 thien-do

I like this idea. I would just call it "differences" rather than "migrating". The differences are that we need to be compatible with the legacy approach from an API input/output point of view. Please go ahead, and thanks again!

tomayac avatar Sep 27 '21 09:09 tomayac

If you're ok, I'd like to have a small PR to add a small section to the README regarding the migration from the native file system.

@thien-do Friendly ping, are you still interested in this?

tomayac avatar Apr 14 '22 15:04 tomayac

Hey @tomayac , sorry I can't do it :(

thien-do avatar Apr 16 '22 14:04 thien-do