-
Notifications
You must be signed in to change notification settings - Fork 61
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
defer: Deprecate legacyResponse
#337
defer: Deprecate legacyResponse
#337
Conversation
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.
This LGTM! Crazy how little code was actually needed to do this and get such a big performance optimization. We should have done this a long time ago. Thanks so much @calvincestari!
I'm not sure why you changed the indentation styling of a bunch of the code in this PR as well. I prefer the style with params on individual lines, but since we haven't adopted an official style guideline and linter rules, I'm not going to request changes for that. That is something we really should do though 😅 .
I still need to:
|
} | ||
} | ||
|
||
private func parseIncrementalResult() throws -> (IncrementalGraphQLResult, RecordSet?) { |
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.
Ideally the parseResult
and parseResultFast
functions in GraphQLResult
would be internal
rather than the public
scope they have now but that would be a potentially breaking change. These (parseIncrementalResult
and parseIncrementalResultFast
) are scoped minimally for now but we can always loosen that if needed.
820650c
into
feature/defer-execution-networking
Closes apollographql/apollo-ios#3370.
legacyResponse