Skip to content

Commit 309e772

Browse files
thefourtheyeaddaleax
authored andcommitted
doc: update behaviour of fs.writeFile
As per the decision in #23433, the `fs.writeFile` will always write from the current position if it is used with file descriptors. This patch updates it. Ref: #23709 PR-URL: #25080 Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Weijia Wang <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Anto Aravinth <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]> Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
1 parent 0066fdb commit 309e772

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/api/fs.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -3614,10 +3614,10 @@ recommended.
36143614
1. Any specified file descriptor has to support writing.
36153615
2. If a file descriptor is specified as the `file`, it will not be closed
36163616
automatically.
3617-
3. The writing will begin at the beginning of the file. For example, if the
3618-
file already had `'Hello World'` and the newly written content is `'Aloha'`,
3619-
then the contents of the file would be `'Aloha World'`, rather than just
3620-
`'Aloha'`.
3617+
3. The writing will begin at the current position. For example, if the string
3618+
`'Hello'` is written to the file descriptor, and if `', World'` is written with
3619+
`fs.writeFile()` to the same file descriptor, the contents of the file would
3620+
become `'Hello, World'`, instead of just `', World'`.
36213621

36223622

36233623
## fs.writeFileSync(file, data[, options])

0 commit comments

Comments
 (0)