Unix commands vs. fs-extra functions

[manidlou]

Something that I keep seeing in users' comments is that users expect fs-extra functions to have the same behavior/implementation as unix commands cp, mv, rm....

At least, I couldn't find anywhere in the docs that specifies we follow unix or posix or any other specs.

I think it is a good idea to clarify this for our users. So my question is, what should we do here? Should we follow some specs or we should specify in the docs that we don't follow any specs?

[RyanZim]

I'm not interested in following specs for command-line *nix tools. The assumption probably comes from our function naming; also this could be improved:

node-fs-extra/package.json

Line 4 in a6b1a44

"description": "fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf.",

[manidlou]

Yeah I'm not interested in following specs neither! I just wanna make sure it is clear for our users that we don't follow any specs and they shouldn't expect fs-extra functions to have the same behavior as unix commands.

[RyanZim]

Do you want to submit a docs PR for this? Feel free to improve the npm description while you're at it.

[RyanZim]

Looking closer, copy*, ensureDir*, & remove* all contain statements such as:

Like cp -r.

Should we remove these statements, or clarify that they're similar, but not the same?

[RyanZim]

@manidlou bump

[manidlou]

I would say we remove them (I am still fine if you guys decide to edit them to be clear) but I don't understand how this would be helpful to users because they are ultimately different implementations and I think keeping them in the docs still leave some confusion around this!