Use same field name for pagination that compiler generates#4317
Use same field name for pagination that compiler generates#4317dwwoelfel wants to merge 1 commit intofacebook:mainfrom
Conversation
|
Hi @dwwoelfel! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
I think this is a duplicate of #4053? |
|
Closing for now. Feel free to ping here if this is different than #4053. |
It looks like the compiler generates the refetchable query using the
nodeInterfaceIdFieldas the variable name, but the runtime always uses "id" as the variable name.This should fix
usePaginationFragmentfor users that set a customnodeInterfaceIdFieldin theirschemaConfig.