-
Notifications
You must be signed in to change notification settings - Fork 59
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
fix: DataDict
initialization of deferredFragments
#557
fix: DataDict
initialization of deferredFragments
#557
Conversation
✅ Docs Preview ReadyNo new or changed pages found. |
✅ Deploy Preview for eclectic-pie-88a2ba ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for apollo-ios-docc canceled.
|
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.
LGTM. Great fix!
|
||
var deferredFragments: OrderedSet<String> = [] | ||
|
||
let nameGenerator: (_ typeInfo: SelectionSet.TypeInfo) -> String = { typeInfo in |
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.
Love this pattern. Very clean!
6db35551 fix: `DataDict` initialization of `deferredFragments` (#557) git-subtree-dir: apollo-ios-codegen git-subtree-split: 6db35551c7bc0879b61539c08338253a7b4a146b
…of `deferredFragments` git-subtree-dir: apollo-ios-codegen git-subtree-mainline: 9c595a8 git-subtree-split: 6db35551c7bc0879b61539c08338253a7b4a146b
While working on selection set initializers I realized that the current generated initializers do not set the selection set types in the
deferredFragments
property.Some of the named fragment initializers do not look correct but I believe this is due to apollographql/apollo-ios#3486 and apollographql/apollo-ios#3487. Adding the values to
deferredFragment
will not have any detrimental effect and those will get fixed on top of this work.