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.
RemoteResource.find_by
raises aRemoteResource::HTTPNotFound
error if the resource can't be found. This is unexpected asActiveRecord::Base.find_by
doesn't raise when the record can't be found.ActiveRecord::Base.find_by!
does raise an error.Current implementation:
Having a
RemoteResource.find_by
method that doesn't raise can be useful, as we currently rescue theRemoteResource::HTTPNotFound
error instead in a lot of places. To make RemoteResource behave more like ActiveRecord and have separate finder methods that raise or returnnil
we can add a.find_by!
method that raises and let.find_by
returnnil
instead:As
.find_by
is used a lot, we deprecate it first in this PR. In version 2.0 we can make.find_by
returnnil
instead.This PR: