-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recursive filesystem operations api #78
Comments
I commented in the meeting that much usage of these api's probably comes from a handful of fs wrapper libraries. To follow up on those, here are the most popular ones I know of:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've got some feedback on the recursive
rmdir
API; see nodejs/node#34278Given that the
recursive
option is still experimental, we can still break it, if necessary. Note that therecursive
option formkdir
is not marked experimental.This may be a good topic for a deep-dive session as noted by @bengl in #73. Also, input on API design from @nodejs/fs would be helpful.
Questions include, but are not limited to:
fs.rmdir
? e.g.,allowRetries
,force
fs
module? Even if not, should we stay out of it anyway?fs.rmdir
w/recursive
actually functions likerm -f
if given a file instead of a directory. Should it do that?Note: It does not sound like outright removal of this functionality is being suggested anywhere.
It's pretty clear to me, anyway, that the current API is a product of various constraints, and not necessarily technical ones...
The text was updated successfully, but these errors were encountered: