RespondsTo matcher added

[AlexDenisov]

With this matcher you're able to check if class or instance responds to some selector, via @selector or NSString, e.g.:

[NSObject class] should responds_to(@selector(new));
@"Buzz" should responds_to(@"length");

[idoru]

Thank you for your contribution.

Could you change the wording from responds_to to respond_to?

Also, we prefer to use NSSelectorFromString() for non-existent selectors in our codebase, rather than ignoring the diagnostic.

[AlexDenisov]

Ok, I will update this PR.

[AlexDenisov]

@idoru, done. Could you review changes?

[jeffh]

Shouldn't it be a cstring instead of NSString to be similar to have_received and the like?

[AlexDenisov]

@jeffh, that's make sense. What about third one method with cstring in addition to the existing methods?

[jeffh]

That works.

—
Sent from my iPhone

On Tue, Oct 29, 2013 at 12:52 PM, Alexey Denisov notifications@github.com
wrote:

@jeffh, that's make sense. What about third one method with cstring in addition to the existing methods?

Reply to this email directly or view it on GitHub:
#132 (comment)

[AlexDenisov]

That works.

What do you mean?

[idoru]

Good catch @jeffh.

We should ensure both SEL and c-strings are supported (for consistency with HaveReceived).

Supporting NSString would make it inconsistent with other method name matchers; The c-string format was provided as a short-hand, is there a reason why NSString would be useful? If so, we'll add it with a mind to support NSString elsewhere in future. If not, I think just SEL and c-strings are all we should support.

[AlexDenisov]

@idoru, I got it.

[idoru]

Great!

Thanks for your contribution and being so flexible.

[AlexDenisov]

You're welcome!