resolveReferences for _raw fields has no impact

[sanity-io]

resolveReferences for _raw fields has no impact

[chandlervdw]

This fixes the unresolved refs issue: #66

[roffelsaurus]

I did more research and an attempt at fixing this today.

• no references work as expected and gives you a usable portable(despite #37 claiming otherwise)

document {
   object {
      _rawPortable
   }
}

• top level field portable with refs work

document {
      _rawPortable(resolveReferences: {maxDepth: 10})
}

• but portable nested in object does not dereference the { _ref } objects

document {
   object {
      _rawPortable(resolveReferences: {maxDepth: 10})
   }
}

I got annoying error like "_rawTitle: incorrect OutputType: JSON"from graphql-compose when using npm link on gatsby-source-sanity into my gatsby project, so couldn't actually debug this properly, but just using DEBUG=sanity gave a clue that
resolveReferences was called for the object with _ref, but it gave the error message here:

gatsby-source-sanity/src/util/resolveReferences.ts

Line 50 in c83a418

debug(`Could not resolve reference to ID "${targetId}"`)

[rexxars]

Does the referenced document still exist? I see the reference is set to weak.

[intensr]

Hey Espen,
yes I log several items which all are referenced to different documents, but good point.

[intensr]

@rexxars is there any news on this?

[chandlervdw]

I, too, have this issue, though I don't have any _weak attribute within my unique mark attribute object.

[intensr]

I investigated a bit further.

Lets say you have those two document types (just for testing purposes)

export default {
  name: 'page',
  title: 'Page',
  type: 'document',
  fields: [
    {
      name: 'link',
      title: 'Link',
      type: 'reference',
    }
  ]
}

and

export default {
  name: 'job',
  title: 'Job',
  type: 'document',
  fields: [
    {
      name: 'page',
      title: 'Page',
      type: 'page',
    },
  ],
};

The reference of page will work where the reference of jobs wont work so i guess theres a type nesting problem regarding reference types

I would be available to go through it in google meet or so to investigate further with you @rexxars if you would like

[roffelsaurus]

this does work for documents referenced to from inside blockcontent. I use a catch all depth 10 on all graphql queries on blockcontent. could perhaps your nesting be deeper than 10?

[intensr]

roffelsaurus to the rescue !
can you describe closer what you mean with catch all ?
regarding the deeper than 10 thing, i've set it to 5000 just to try but that had no impact.

[chandlervdw]

I am also seeing unresolved references when they are nested

[roffelsaurus]

Nothing special, just a suggestion to try deeper maxdepth. If 5000 did not work there is sonething else with your model compared to mine. tir. 4. feb. 2020 kl. 20:43 skrev Chandler Van De Water < [email protected]>:

…

I am also seeing unresolved references when they are nested — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#43?email_source=notifications&email_token=AAKOKWOSBBMRBSY2SRKXOXTRBHAOTA5CNFSM4JBUD6L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKY5ZZY#issuecomment-582081767>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKOKWITFNFF6S26ZIZQTJTRBHAOTANCNFSM4JBUD6LQ> .

[chandlervdw]

For me, it doesn't resolve image references within any bodyPortableText blocks