refactor!: split file handles into seperate function #117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Removes the handling of
FileSystemFileHandle
arrays from thefromEvent()
function, and moves it to a dedicatedfromFileHandles()
function purposefully made for handling this data type. This reduces the need to handle polymorphic input and narrow down what the exact type should be infromEvent()
. Additionally, this allows bundlers to more effectively tree-shake the module in case the other code is never used.Does this PR introduce a breaking change?
Yes, arrays of
FileSystemFileHandle
are now handled in a dedicatedfromFileHandles()
function. Users that were previously usingfromEvent()
will now have to use this dedicated function instead.Other information
This also removes the notice that this feature is experimental, promoting
fromFileHandles()
to a stable API in the next major.