-
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?
Conversation
See discussion at #777 (comment) with @crazytonyli
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 comment
The reason will be displayed to describe this comment to others. Learn more.
I believe you can do endpointError.apiErrorCode
instead of using errorUserInfo
.
return | ||
} | ||
|
||
let status = RewindStatus(state: .unavailable) | ||
success(status) | ||
failure(endpointError) |
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.
The original code returns error
. But there it's changed to endpointError
. I don't think we should change it here?
// 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 error.castedToEndpointErrorWitCode(.preconditionFailure) != nil else { | ||
success(RewindStatus(state: .unavailable)) | ||
return | ||
} |
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?
See discussion at
#777 (comment) with @crazytonyli
Testing Details
See green CI.
CHANGELOG.md
if necessary. — N.A.