Update non-normative text for DirectoryHandle's removeEntry() #166
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.
This change updates only the non-normative section for
FileSystemDirectoryHandle's removeEntry() method.
It clarifies that the Promise is rejected with a "NotFoundError"
DOMException when an entry corresponding to the
name
parameter doesnot exist.
Further, it adds that the Promise is rejected with an
"InvalidModificationError" DOMException when attempting to remove a
non-empty directory with the
recursive
option set to false.These updates were made to align the non-normative text with the
algorithm for removeEntry() outlined in the File System Standard.
See here: https://fs.spec.whatwg.org/#api-filesystemdirectoryhandle-removeentry
Preview | Diff