Uh oh!
There was an error while loading. Please reload this page.
fs: improve error messages - #675
Conversation
piscisaureus
commented
Jan 30, 2015
There was a problem hiding this comment.
That comment was already there. I believe the motivation for putting it there was that uv error codes are meaningless to the user, because there is no way to know what their values are.
bnoordhuis
commented
Jan 31, 2015
LGTM but see comment. I tagged this semver-minor because the API (but not the ABI) is backwards/source compatible. NODE_MODULE_VERSION should be bumped. |
bnoordhuis
commented
Jan 31, 2015
Come to think of it, you can probably make it ABI-compatible by having an overload instead of adding a new parameter. |
piscisaureus
commented
Jan 31, 2015
I was thinking the same, but I noticed how many overloaded error functions we already had... But ok, everything for a stable ABI I guess. |
piscisaureus
commented
Jan 31, 2015
@bnoordhuis updated, ptal |
* Include a description for the error message * For rename, link, and symlink, include both the source and destination path in the error message. * Expose the destination path as the `dest` property on the error object. * Fix a bug where `ThrowUVException()` would incorrectly delegate to `Environment::TrowErrnoException()`. API impact: * Adds an extra overload for node::UVException() which takes 6 arguments. PR: nodejs#675Fixes: nodejs#207Closes: nodejs#293 Reviewed-by: Ben Noordhuis <info@bnoordhuis.nl>
bnoordhuis
commented
Jan 31, 2015
LGTM |
path in the error message.
destproperty on the error object.API impact:
This is an alternative for #293
R=@iojs/tc