-
Notifications
You must be signed in to change notification settings - Fork 6
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
Frameworks #15
Frameworks #15
Conversation
Oh and I removed the |
@@ -0,0 +1,15 @@ | |||
@import UIKit; | |||
|
|||
#define ExtendTraitEnvironment(specific_class) \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would've done this with Swift protocol extensions but couldn't get it figured out.
PODFILE CHECKSUM: 2c0c73dfeef5174af308d83c7d6c5ec25554150d | ||
|
||
COCOAPODS: 1.0.0.beta.2 | ||
COCOAPODS: 0.39.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tsk tsk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Send a PR with a Gemfile 😛
OK, updated to CocoaPods 1.0 beta thingy, also split out mock-specific stuff into the subspec. |
ace |
OK so this does a lot:
has_include
weirdness, so I took it out and moved mock-related stuff just to theMocks
subspec. This makes it easier to maintain, but it's a breaking change, but we're pre-1.0 so following the CocoaPods philosophy: http://media3.giphy.com/media/DHgmBovno9Mli/giphy.gifUITraitEnvironment
:UIView
andUIViewController
.Note that I chose stubbing as an approach instead of something else. Why? The
UITraitEnvironment
protocol contains the logic we're trying to stub, a readonly property. Subclassing was considered but every class-under-test would need to be subclassed, which is a pain. Stubbing works.Fixes #13.