How to exclude the URL parameter in a Gatsby page query if the public field is false.

I have this query: query { courses: allSanityCourses { nodes { price name playlist { title url public } } } } Is it possible to not send the url parameter to the component if the public field is false? The frontend code cannot have this URL in it.

This is in the context of a Gatsby page query which runs at build time.

Sure, here’s an example with

select

:
https://groq.dev/x6jAjBKFZK7zc94QfNMpEG

Or its sugar form

ah I’ve just realized you’re doing this with Graphql in Gatsby. You can add resolver with Gatsby’s createSchemaCustomization. See the docs here:

https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization/

Hey , thanks for the link! I’ve tried:exports.createSchemaCustomization = ({ actions, schema }) => {
const { createTypes } = actions
const typeDefs = [
schema.buildObjectType({
name: “SanityCourses”,
fields: {
playlist: {
type: “[SanityVideo]“,
url: {
type: “String”,
resolve: (source) => {
console.log(source)
return “nope”
}
},
},
},
interfaces: [“Node”],
}),
]
createTypes(typeDefs)
}

But the url does not change. Any idea how to target that nested “url” field?

Hey , IIRC for this you’d have to find the type of the

playlist

field (perhaps

SanityCoursePlaylist

or something like that, you can find out in graphiq), then modify that type instead of the

SanityCourses

type. Hope that make sense!

Hey , Corey got the answer right on SO: https://stackoverflow.com/questions/68733466/how-to-create-custom-resolvers-for-gatsby-page-queries/68734000

Nice! I usually reach for

createSchemaCustomization

first, but what says make sense. For adding a computed field like this, createResolver definitely fits the bill since it run lasts (IIRC)