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
It is common for IDEs and game-engine editors to specify resources using URIs or file paths.
To access a deeply nested file, we need to call getFileHandle and getDirectoryHandle recursively. Each level is an asynchronous operation that needs to be run sequentially.
I propose that the getFileHandle, getDirectoryHandle, and removeEntry methods be overloaded to accept an array/iterable argument.
Each level makes at least one file system call to check if the file exists. This takes anywhere between .2 to 1 milliseconds on the devices I've tried. The difference adds up quickly when processing multiple files.
It is common for IDEs and game-engine editors to specify resources using URIs or file paths.
To access a deeply nested file, we need to call
getFileHandle
andgetDirectoryHandle
recursively. Each level is an asynchronous operation that needs to be run sequentially.I propose that the
getFileHandle
,getDirectoryHandle
, andremoveEntry
methods be overloaded to accept an array/iterable argument.Alternatively, file names should accept slashes as delimiters.
The options parameter should include a
createRecursive
flag to complement thecreate
flag.The text was updated successfully, but these errors were encountered: