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

Xcode 10 support #51

Merged
merged 4 commits into from
Jun 8, 2018
Merged

Xcode 10 support #51

merged 4 commits into from
Jun 8, 2018

Conversation

sharplet
Copy link
Contributor

@sharplet sharplet commented Jun 7, 2018

The main fix was a case where we were overloading a computed property based on
return type, which no longer works in Swift 4.2

For compatibility with testing frameworks
Copy link

@asmallteapot asmallteapot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@@ -418,7 +418,7 @@ extension SignalProtocol where Value: OptionalProtocol, Value.Wrapped: AnyObject
}

extension Action {
fileprivate var isEnabled: RACSignal<NSNumber> {
fileprivate var _isEnabled: RACSignal<NSNumber> {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: rename to isEnabledSignal?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or possibly racIsEnabled or rac_isEnabled? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm happy with isEnabledSignal 👍 thanks!

Swift 4.2 doesn't seem to be able to handle properties overloaded on
return type, which results in this failing to type check. Using an
alternative name for the private property works around the problem.
@@ -1113,6 +1113,7 @@
"$(PROJECT_DIR)/build/Debug",
);
INFOPLIST_FILE = ReactiveObjCBridgeTests/Info.plist;
MACOSX_DEPLOYMENT_TARGET = 10.10;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: I only changed these deployment targets in test targets.

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.

2 participants