gqlOutputFieldResolvers will not work for nestedType on customQuery

[leonahliang90]

Bug report

Describe the bug

version of "@keystonejs/fields": "^12.0.1"

To Reproduce

1. I created my own customQuery,and within it, will execute an existing graphql query and the end result is returned with expanded data structure.
   

2. however, when the expanded data structure which is passed into the gqlOutputFieldResolvers again, we will be hitting with some error, as the data being passed is not items with raw ID, instead they are object with expanded data structure from step 1.
   

3. Not too sure if i clarify the issue clear enough, however, i have created my own Temporary solution, which is i will replace the object back with raw ID so that the desired params will be passed into gqlOutputFieldResolvers successfully.

[stale]

It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :)

[bladey]

Keystone 5 has officially moved into active maintenance mode as we push towards the next major new version Keystone Next, you can find out more information about this transition here.

In an effort to sustain the project going forward, we're cleaning up and closing old issues such as this one. If you feel this issue is still relevant for Keystone Next, please let us know.