Skip to content

Commit

Permalink
Revert "doc: clarify fs.symlink and fs.symlinkSync parameters"
Browse files Browse the repository at this point in the history
The offending doc change clarified nothing, but put the arguments to
fs.symlink() and fs.symlinkSync() in the wrong order.

This reverts commit 8146f2e.

BUG: nodejs/node-v0.x-archive#8920
PR: nodejs/node-v0.x-archive#8936
  • Loading branch information
piscisaureus committed Jan 27, 2015
1 parent 668bde8 commit 5843ae8
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/api/fs.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,7 @@ the completion callback.

Synchronous link(2).

## fs.symlink(srcpath, dstpath[, type], callback)
## fs.symlink(destination, path[, type], callback)

Asynchronous symlink(2). No arguments other than a possible exception are given
to the completion callback.
Expand All @@ -217,7 +217,7 @@ is `'file'`) and is only available on Windows (ignored on other platforms).
Note that Windows junction points require the destination path to be absolute. When using
`'junction'`, the `destination` argument will automatically be normalized to absolute path.

## fs.symlinkSync(srcpath, dstpath[, type])
## fs.symlinkSync(destination, path[, type])

Synchronous symlink(2).

Expand Down

0 comments on commit 5843ae8

Please sign in to comment.