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.

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

The class should equal, not the other way round #11

Merged
merged 1 commit into from Apr 3, 2014

Conversation

julz
Copy link
Contributor

@julz julz commented Apr 3, 2014

Replaced various instances of foo.should.class with foo.class.should. As
well as reading better, the latter version actually tests something :).

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: http://www.pivotaltracker.com/story/show/68803944. This repo is managed by the 'Runtime' team.

Replaced numerous instances of `foo.should.class` with `foo.class.should`. As
well as reading better, the latter version actually tests something.
@karlkfi
Copy link
Contributor

karlkfi commented Apr 3, 2014

Looks good to me.

There might be a conversation here about whether we want to use should eq instead of should ==, but it looks like the convention so far for this file is should ==.

@MarkKropf You want this test bug fix in the Runtime backlog?

CF Community Pair (@karlkfi & @khwang1)

karlkfi added a commit that referenced this pull request Apr 3, 2014
The class should equal, not the other way round
@karlkfi karlkfi merged commit 4de7686 into cloudfoundry:master Apr 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants