-
Notifications
You must be signed in to change notification settings - Fork 263
Define XCTestCaseClosure typealias #204
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
Conversation
I like it! Could we brainstorm some additional names, tough? In the context of the XCTest framework, |
Of course! I choose XCTestClosure because I tend to favor shorter names. Initially I was thinking in XCTestCaseClosure, but I also like XCTestMethodClosure. Let me know which one you prefer and I will make the change. |
Personally I like |
ccfc1de
to
2b84b35
Compare
@modocache I changed it to |
public typealias XCTestCaseEntry = (testCaseClass: XCTestCase.Type, allTests: [(String, (XCTestCase) throws -> Void)]) | ||
public typealias XCTestCaseEntry = (testCaseClass: XCTestCase.Type, allTests: [(String, XCTestCaseClosure)]) | ||
|
||
public typealias XCTestCaseClosure = (XCTestCase) throws -> Void |
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.
Sorry, a bit of a nit-pick: how about moving this typealias
above the first, so that readers don't encounter XCTestCaseClosure
before it's defined?
Also, this typealias could use some documentation.
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 totally agree!
Let me know if the documentation is helpful or it needs improvements.
Great, looks good to me! Thanks. @swift-ci please test |
There was some problem with the merge? |
@swift-ci Please test |
Thanks guys, this does look good! |
I believe the following type alias can improve the readability of the code, what do you think?