fsIO - realPath: re-raise ENOENT javascript exceptions as NoSuchFileException #2759
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
armanbilge
reviewed
Dec 19, 2021
Comment on lines
324
to
327
| F.fromPromise(F.delay(fsPromisesMod.realpath(path.toString))).map(Path(_)).recoverWith { | ||
| case NoSuchFileException(e) => | ||
| F.raiseError(e) | ||
| } |
There was a problem hiding this comment.
I think this is equivalent to:
.adaptError { case NoSuchFileException(ex) => ex }There was a problem hiding this comment.
Aha! Nice! I've completely forgotten about this one :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
calls to
realPathin nodejs throw anENOENTexception if the path doesn't exist. In order to align the behaviour ofrealPathwith what we have in JVM, those errors are re-raised as aNoSuchFileException.