Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should beEmpty() match against nil? #62

Closed
jeffh opened this issue Nov 21, 2014 · 2 comments · Fixed by #66
Closed

Should beEmpty() match against nil? #62

jeffh opened this issue Nov 21, 2014 · 2 comments · Fixed by #66
Labels
enhancement question / needs more details
Milestone
v0.2.0

Comments

@jeffh
Copy link
Member

jeffh commented Nov 21, 2014

No description provided.

jeffh referenced this issue in jeffh/Nimble Nov 21, 2014
@jeffh
Objective-C matchers properly check for nil values.
9a3256e 
Refactors.
@paulyoung
Copy link

I would expect it not to.

@modocache
Copy link
Member

I'd say no. It'd be quite surprising.

@modocache modocache mentioned this issue Nov 21, 2014
Merged
@jeffh jeffh modified the milestone: v0.2.0 Nov 21, 2014
jeffh added a commit to jeffh/Nimble that referenced this issue Nov 25, 2014
@jeffh
beEmpty() matcher no longer matches against nil.
1cc6d84 
in: expect(nil).to(beEmpty());

Closes Quick#62.
@jeffh jeffh mentioned this issue Nov 25, 2014
Merged
@jeffh jeffh closed this as completed in #66 Nov 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement question / needs more details
Projects
None yet
Milestone
v0.2.0
Development

Successfully merging a pull request may close this issue.

beEmpty() matcher no longer matches against nil. jeffh/Nimble
3 participants
@jeffh @paulyoung @modocache