-
Notifications
You must be signed in to change notification settings - Fork 16
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
Avoid casting to NSError
in favor of WordPressApiError
#779
base: trunk
Are you sure you want to change the base?
Changes from 1 commit
80ac1e9
568d67f
9d5aa85
794f03f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -152,18 +152,15 @@ open class ActivityServiceRemote: ServiceRemoteWordPressComREST { | |
failure(ResponseError.decodingFailure) | ||
} | ||
}, failure: { error, _ in | ||
// FIXME: A hack to support free WPCom sites and Rewind. Should be obsolote as soon as the backend | ||
// stops returning 412's for those sites. | ||
let nsError = error as NSError | ||
|
||
guard nsError.domain == WordPressComRestApiEndpointError.errorDomain, | ||
nsError.code == WordPressComRestApiErrorCode.preconditionFailure.rawValue else { | ||
failure(error) | ||
// FIXME: A hack to support free WPCom sites and Rewind. | ||
// Should be obsolete as soon as the backend stops returning 412's for those sites. | ||
guard let endpointError = error.castToEndpointErrorWitCode(.preconditionFailure) else { | ||
success(RewindStatus(state: .unavailable)) | ||
return | ||
} | ||
|
||
let status = RewindStatus(state: .unavailable) | ||
success(status) | ||
failure(endpointError) | ||
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. The original code returns |
||
|
||
return | ||
}) | ||
} | ||
|
@@ -222,3 +219,24 @@ private extension ActivityServiceRemote { | |
} | ||
|
||
} | ||
|
||
private extension Error { | ||
|
||
func castToEndpointErrorWitCode( | ||
_ code: WordPressComRestApiErrorCode | ||
) -> WordPressComRestApiEndpointError? { | ||
guard let apiError = self as? WordPressAPIError<WordPressComRestApiEndpointError> else { | ||
return .none | ||
} | ||
|
||
guard case .endpointError(let endpointError) = apiError else { | ||
return .none | ||
} | ||
|
||
guard endpointError.code == code else { | ||
return .none | ||
} | ||
|
||
return endpointError | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -84,11 +84,17 @@ public class JetpackServiceRemote: ServiceRemoteWordPressComREST { | |
completion(false, JetpackInstallError(type: .installResponseError)) | ||
} | ||
}) { error, _ in | ||
let error = error as NSError | ||
let key = error.userInfo[WordPressComRestApi.ErrorKeyErrorCode] as? String | ||
let jetpackError = JetpackInstallError(title: error.localizedDescription, | ||
code: error.code, | ||
key: key) | ||
guard let apiError = error as? WordPressAPIError<WordPressComRestApiEndpointError>, | ||
case .endpointError(let endpointError) = apiError else { | ||
completion(false, nil) | ||
return | ||
} | ||
|
||
let jetpackError = JetpackInstallError( | ||
title: endpointError.localizedDescription, | ||
code: endpointError.errorCode, | ||
key: endpointError.errorUserInfo[WordPressComRestApi.ErrorKeyErrorCode] as? String | ||
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. I believe you can do |
||
) | ||
completion(false, jetpackError) | ||
} | ||
} | ||
|
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.
My brain can't process these two guard statements. But, are their logic changed?
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 noticed an unit test failed, I think this guard change here might be the cause?