-
Notifications
You must be signed in to change notification settings - Fork 177
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
Support calling objective-c methods and closures with nil #374
Open
dekpient
wants to merge
1
commit into
Brightify:master
Choose a base branch
from
dekpient:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -160,6 +160,39 @@ class ObjectiveClassTest: XCTestCase { | |
|
||
objcVerify(mock.dudka(lelo: objcAny())) | ||
} | ||
|
||
func testSwiftClassWithNullableArgs() { | ||
let expectCompleteWithNil = expectation(description: "Should call completion with nil") | ||
let expectNilArg = expectation(description: "Should call with nil") | ||
|
||
let mock = objcStub(for: SwiftClass.self) { stubber, mock in | ||
stubber.when(mock.say("cheeze", completion: objcAnyClosure())).then { args in | ||
let completionHandler = objectiveOptionalArgumentClosure(from: args[1]) as (String, [String]?) -> Void | ||
completionHandler("meh", nil) | ||
} | ||
stubber.when(mock.say(nil, completion: objcAnyClosure())).then { args in | ||
let completionHandler = objectiveArgumentClosure(from: args[1]) as (String, [String]?) -> Void | ||
completionHandler("nil now behaves", []) | ||
} | ||
} | ||
|
||
mock.say("cheeze") { result, messages in | ||
XCTAssertEqual("meh", result) | ||
XCTAssertNil(messages) | ||
expectCompleteWithNil.fulfill() | ||
} | ||
|
||
mock.say(nil) { result, messages in | ||
XCTAssertEqual("nil now behaves", result) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good |
||
XCTAssertEqual([], messages) | ||
expectNilArg.fulfill() | ||
} | ||
|
||
wait(for: [expectCompleteWithNil, expectNilArg], timeout: 1) | ||
|
||
objcVerify(mock.say("cheeze", completion: objcAnyClosure())) | ||
objcVerify(mock.say(nil, completion: objcAnyClosure())) | ||
} | ||
} | ||
|
||
class SwiftClass: NSObject { | ||
|
@@ -168,6 +201,11 @@ class SwiftClass: NSObject { | |
dynamic func dudka(lelo: String) -> Bool { | ||
return false | ||
} | ||
|
||
@objc | ||
dynamic func say(_ message: String?, completion: @escaping (String, [String]?) -> Void) -> Void { | ||
// mock me | ||
} | ||
} | ||
#else | ||
#warning("macOS tests are missing.") | ||
|
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.
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.
I think we'll have to try coming up with a more complex solution to this, because as the number of arguments go up, the combinations of optional and non-optional arguments will skyrocket.
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.
Yeah, I agree. I ended up defining this in my test project just for the specific test cases that I need. Should I split this into 2 PRs so the 1st problem can be fixed? I really need that fix.
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.
Splitting this up sounds like the better call at the moment. Would you please add the remaining combinations for 2-parameter closures, i.e. (optional, non-optional), (non-optional, optional) as well as an optional counterpart to the 1-parameter closure. We'll need to come up with a more generic solution, but for now this can help make the closures more accessible by showing users how to implement them (only using the right amount of arguments). Thanks!
Also, would you mind creating a test or two for the closures with optional parameters? Just to make sure they work and when replacing with the generic solution to know nothing has been broken.
Afterwards, we can probably merge this and release.