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.
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
Refactor CrystalPath::Error #9359
Refactor CrystalPath::Error #9359
Changes from 1 commit
e9e9849
df90661
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move this rescue just around
find_in_path
because that's where the error can happen? This makes it much clearer when the exception is expected to happen.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered that, but the problem is that the exception raised there would subsequently be rescued in line 89. I don't think it makes sense to make that rescue handler work around that.
A slightly less confusing option could be to create the error in a rescue around
find_in_path
, assign it to a local variable and only raise in anelse
rescue handler. Not sure if that's worth it, though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see. Yeah, let's leave it like that for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That said, I don't understand why
CrystalPath::NotFoundError
is handled in a special way here, instead of just being a regular Crystal::Exception and having a sensibleto_s
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea was to have
CrystalPath::NotFoundError
as a plain internal error type, not related to any user code interpretation.CrystalPath
should not care wheter it was invoked for arequire
or something else. It also doesn't know the code location, so it can't really create a proper user-facing error.NotFoundError
just communicates that finding a path failed. What that means depends on the context. In the context of interpreting aRequire
node it means the require has failed and an appropriate error is raised for that specific situation.