Add status predicate methods to Response#respond_to? #482
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.
Expands the existing
respond_to?
first-party method list to include the HTTP status predicates. Useful for things like RSpec, which checkrespond_to?
when using predicate matchers - beyond that it makes for a more consistent and predictable object (If I can call it, it shouldrespond_to?
).Because
Response
inherits fromBasicObject
we miss out on quite a few of these pre-made tools fromObject
, though it looked like moving away fromBasicObject
was a bigger task and would require a bit more debate. I figured this was the simplest change to make.I have not checked for other methods that could be added to
RESPOND_TO_METHODS
, my concern was with the predicate methods.