-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
doc: Correct note on behavior of stats.isDirectory #50946
Conversation
Can you please fix the first commit message so that it adheres to our commit message guidelines? Thank you. |
@lpinca Is there a way to do that through GitHub, or does this require force-pushing new commits? |
It requires force pushing. |
@lpinca Okay -- unless I've misunderstood the lint, this should be OK now. |
Co-authored-by: Luigi Pinca <luigipinca@gmail.com>
Trying again. |
Landed in 135948d |
PR-URL: #50946 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #50946 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Original author incorrectly assumed that lstat can only be used on symbolic links
The note incorrectly stated that
.isDirectory()
always returns false when the stats object was obtained fromfs.lstat()
.lstat
can be used on any type of object -- not just symbolic links. When stats are obtained using lstat for a regular directory (not a link),.isDirectory()
will return true.