kristofferstrube / blazor.filesystem

A Blazor wrapper for the File System browser API.

Kristoffer Strube

I'm currently working on using Blazor Web Apps to work with the browser easily and safely.

Right now, I'm focusing on wrapping the Web Audio API and its surrounding API's in my Blazor.WebAudio and Blazor.MediaCaptureStreams projects.

My Blog: https://kristoffer-strube.dk

I also do consultancy primarily focused on Blazor. If you are interested in my services, just contact me on Twitter or LinkedIn. Jobs related to my open-source projects get a considerable rebate.

Contact

Twitter 🐤: @KStrubeG

LinkedIn 👔: KristofferStrube

Mastodon 🐘: @KristofferStrube

BlueSky 🦋: @kstrubeg.bsky.social

blazor.filesystem's Issues

Casting between `FileSystemHandleInProcess` and `FileSystemFileHandleInProcess` or `FileSystemDirectoryHandleInProcess` is not possible.

When we get all the entries of a directory using the ValuesAsync method of FileSystemDirectoryHandleInProcess it currently returns an array of FileSystemHandleInProcess. As the current inheritance hierarchy is we can't cast each entry to either a FileSystemFileHandleInProcess or a FileSystemDirectoryHandleInProcess as they don't inherit from it.
The following is our current inheritance tree:

  graph LR;
  subgraph Blazor Server Supported
    FileSystemHandle
    FileSystemFileHandle
    FileSystemDirectoryHandle
  end
  subgraph Blazor WebAssembly Only
    FileSystemHandleInProcess
    FileSystemFileHandleInProcess
    FileSystemDirectoryHandleInProcess
  end
  FileSystemFileHandle--->FileSystemHandle
  FileSystemDirectoryHandle--->FileSystemHandle
  FileSystemHandleInProcess--->FileSystemHandle
  FileSystemFileHandleInProcess--->FileSystemFileHandle
  FileSystemDirectoryHandleInProcess--->FileSystemDirectoryHandle

We would ideally have FileSystemDirectoryHandleInProcess inherit from both FileSystemDirectoryHandle and FileSystemHandleInProcess and the same should apply to the file handle.

A solution to this is to use interfaces. If we add two interfaces then the desired cast should be possible, but we will need to change what is returned for a few methods.

  graph LR;
  subgraph Blazor Server Supported
    FileSystemHandle
    FileSystemFileHandle
    FileSystemDirectoryHandle
    IFileSystemHandle
  end
  subgraph Blazor WebAssembly Only
    FileSystemHandleInProcess
    FileSystemFileHandleInProcess
    FileSystemDirectoryHandleInProcess
    IFileSystemHandleInProcess
  end
  FileSystemFileHandle--->FileSystemHandle
  FileSystemDirectoryHandle--->FileSystemHandle
  FileSystemHandleInProcess--->FileSystemHandle
  FileSystemFileHandleInProcess--->FileSystemFileHandle
  FileSystemDirectoryHandleInProcess--->FileSystemDirectoryHandle
  FileSystemHandle-.->IFileSystemHandle
  IFileSystemHandleInProcess-.->IFileSystemHandle
  FileSystemHandleInProcess-.->IFileSystemHandleInProcess
  FileSystemFileHandleInProcess-.->IFileSystemHandleInProcess
  FileSystemDirectoryHandleInProcess-.->IFileSystemHandleInProcess

WriteBlobWriteParams could not be found (even doe the js was loaded)

I was trying to adjust the WriteAsync functions a little (adding a write for a DotNetStreamReference) and stumbled over the fact, that my method added to the js file wasn't found. Same goes for the existing version using "WriteBlobWriteParams".

Am I doing something wrong? Was it tested, cause there is no example using the above.
Could it reference a different IJSObjectReference?

The file is loaded as of what I see in the Devtools sources tab, but I receive an error msg:

Microsoft.JSInterop.JSException: Could not find 'WriteBlobWriteParams' ('WriteBlobWriteParams' was undefined).
blazor.webassembly.js:1 Error: Could not find 'WriteBlobWriteParams' ('WriteBlobWriteParams' was undefined).

Thanks for your reply

Demo not working on iphone IOS

'An unhandled error has occurred. Reload' message received