-
Notifications
You must be signed in to change notification settings - Fork 731
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
Obsolete type GraphQLHTTPResponseError #1425
Comments
Please note that "find usages" isn't the be-all, end-all, especially for enum types - always worth doing a text search through the full codebase. |
The problem here for me was that by not beeing broken because of a removed class my validations got semantically broken because they where still checking for that type. Of course you're right about But still, regarding your advise to check for "usages" with full text search i have to strongly disagree. In fact i heavily rely on this kind of type based analysis and navigating through code and therefore i prefer AppCode over Xcode a lot because of it outstanding capabilities in that. You should give it a try. |
I agree that it's helpful, but particularly when it comes to removing stuff, I've found it better to belt-and-suspenders things by actually searching out where something is used (even in AppCode, which I have used before). |
This has been removed with |
how I can handle server error? |
Try something like this
|
if I write incorrect url here, I cannot handle error and get status code
|
@Max-Job Could you please open this as a different issue and provide more details like:
|
See apollographql/apollo-ios#1425, which affects on not only 0.35.0 but 0.34.0.
See apollographql/apollo-ios#1425, which affects on not only 0.35.0 but 0.34.0.
Bug report
With the new network stack (yeah!) a few types such as
GraphQLHTTPResponseError
became obsolte but did not get removed from code base yet.Versions
apollo-ios
SDK version: 0.34.0Steps to reproduce
"Find usages" of
GraphQLHTTPResponseError
,GraphQLHTTPRequestError
and probably others.The text was updated successfully, but these errors were encountered: