You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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
changed the title
Add tips to migrate from native file system API
Describe differences to directly working with the File System Access API in README
Sep 27, 2021
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:
The text was updated successfully, but these errors were encountered: