build not working about gatsby-source-prismic-graphql HOT 8 CLOSED

It seems weird that i have to rely on the get lodash package when the data should be available on the data.prismic object. Not sure why it's not available at build time?

from gatsby-source-prismic-graphql.

Do we know why the object isn't available at build time?

I just added a console log to your pagination example: https://github.com/birkir/gatsby-source-prismic-graphql/blob/master/examples/pagination/src/templates/article.js

instead of using get i'm trying to access the object directly

console.log(props.data.prismic.allArticles.edges[0].node.title);

and i'm getting the same kind of error

WebpackError: TypeError: Cannot read property 'node' of undefined

Because drafts will not be available on build time, only runtime. This is the nature of Gatsby and the whole purpose of the plugin.

You can either use lodash.get, @babel/plugin-proposal-optional-chaining or ts-optchain if you use typescript.

// lodash get
const title = get(data, 'prismic.allArticles.edges.0.node.title', 'no title yet');

// babel optional chaining
const title = data?.prismic?.allArticles?.edges?[0].?node.?title || 'no title yet';

// ts-optchain
const title = oc(data).prismic.allArticles.edges[0].node.title('no title yet');

I'm closing this issue for now.

from gatsby-source-prismic-graphql.

Have been debugging this for a day or 2 but can't work out why data isn't available at build time. I even console log out the data prop which shows in the build process

and everything is as should be??

from gatsby-source-prismic-graphql.

Maybe the data isn't published yet, but the draft is.

So you have to use lodash/get to ensure its not crashing.

import { get } from 'lodash';
// ...
<h1>{get(data.prismic, 'job_listing.job_title.0.text', 'not found')}</h1>

from gatsby-source-prismic-graphql.

Cheers. Seems there's something going on with thr lifecycle of the data at build time. it appears at build time the local variable 'data' isn't available. If i use the get utility from lodash and pass in the data.prismic object it works?! Wondering what happens with gatsby at build time and what data it has access to and how this differs at runtime in dev mode. I'm guessing dev mode is basically running a mounted app

from gatsby-source-prismic-graphql.

Does the graphql plugin effectively hit the draft state of documents in prismic? or is a payload included with the request and somehow uses the graphql query in the component?

from gatsby-source-prismic-graphql.

Do we know why the object isn't available at build time?

I just added a console log to your pagination example: https://github.com/birkir/gatsby-source-prismic-graphql/blob/master/examples/pagination/src/templates/article.js

instead of using get i'm trying to access the object directly

console.log(props.data.prismic.allArticles.edges[0].node.title);

and i'm getting the same kind of error

WebpackError: TypeError: Cannot read property 'node' of undefined

from gatsby-source-prismic-graphql.

This reminds me of gatsbyjs/gatsby#8790

from gatsby-source-prismic-graphql.