Created
July 26, 2020 15:20
-
-
Save Rubix982/003dcfb3e9ee88c5e26acafe408fecb5 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostSettings". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/Layout.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostSettings". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/Layout.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostSettings". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/meta/ArticleMeta.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostSettings". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/meta/ArticleMeta.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostSettings". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/meta/AuthorMeta.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostSettings". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/meta/AuthorMeta.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostSettings". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/meta/WebsiteMeta.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostSettings". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostSettings" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/components/common/meta/WebsiteMeta.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "cover_image" on type "GhostAuthor". | |
| If you don't expect "cover_image" to exist on the type "GhostAuthor" it is most likely a typo. | |
| However, if you expect "cover_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "cover_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostAuthor": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_description" on type "GhostPost". | |
| If you don't expect "og_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_image" on type "GhostPost". | |
| If you don't expect "og_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_title" on type "GhostPost". | |
| If you don't expect "og_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_description" on type "GhostPost". | |
| If you don't expect "twitter_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_image" on type "GhostPost". | |
| If you don't expect "twitter_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_title" on type "GhostPost". | |
| If you don't expect "twitter_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostPrimary_tag". | |
| If you don't expect "description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostPrimary_tag". | |
| If you don't expect "feature_image" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_title" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostTags". | |
| If you don't expect "description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostTags". | |
| If you don't expect "feature_image" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostTags". | |
| If you don't expect "meta_description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostTags". | |
| If you don't expect "meta_title" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "canonical_url" on type "GhostPost". | |
| If you don't expect "canonical_url" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "canonical_url" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "canonical_url" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "page" on type "GhostPost". | |
| If you don't expect "page" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "page" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "page" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostPost". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostPost". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_styles" on type "GhostPost". | |
| If you don't expect "codeinjection_styles" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_styles" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_styles" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/author.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_description" on type "GhostPost". | |
| If you don't expect "og_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_image" on type "GhostPost". | |
| If you don't expect "og_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_title" on type "GhostPost". | |
| If you don't expect "og_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_description" on type "GhostPost". | |
| If you don't expect "twitter_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_image" on type "GhostPost". | |
| If you don't expect "twitter_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_title" on type "GhostPost". | |
| If you don't expect "twitter_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostPrimary_tag". | |
| If you don't expect "description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostPrimary_tag". | |
| If you don't expect "feature_image" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_title" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostTags". | |
| If you don't expect "description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostTags". | |
| If you don't expect "feature_image" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostTags". | |
| If you don't expect "meta_description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostTags". | |
| If you don't expect "meta_title" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "canonical_url" on type "GhostPost". | |
| If you don't expect "canonical_url" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "canonical_url" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "canonical_url" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "page" on type "GhostPost". | |
| If you don't expect "page" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "page" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "page" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostPost". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostPost". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_styles" on type "GhostPost". | |
| If you don't expect "codeinjection_styles" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_styles" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_styles" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/index.js | |
| There was an error in your GraphQL query: | |
| Unknown type "GhostPage". Did you mean "GhostTag", "GhostPost", "GhostTagEdge", "GhostPostTags", or "GhostPostEdge"? | |
| GraphQL request:2:33 | |
| 1 | | |
| 2 | fragment GhostPageFields on GhostPage { | |
| | ^ | |
| 3 | # Main fields | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/page.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "ghostPage" on type "Query". | |
| If you don't expect "ghostPage" to exist on the type "Query" it is most likely a typo. | |
| However, if you expect "ghostPage" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "ghostPage" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/page.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_description" on type "GhostPost". | |
| If you don't expect "og_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_image" on type "GhostPost". | |
| If you don't expect "og_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_title" on type "GhostPost". | |
| If you don't expect "og_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_description" on type "GhostPost". | |
| If you don't expect "twitter_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_image" on type "GhostPost". | |
| If you don't expect "twitter_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_title" on type "GhostPost". | |
| If you don't expect "twitter_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostPrimary_tag". | |
| If you don't expect "description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostPrimary_tag". | |
| If you don't expect "feature_image" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_title" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostTags". | |
| If you don't expect "description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostTags". | |
| If you don't expect "feature_image" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostTags". | |
| If you don't expect "meta_description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostTags". | |
| If you don't expect "meta_title" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "canonical_url" on type "GhostPost". | |
| If you don't expect "canonical_url" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "canonical_url" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "canonical_url" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "page" on type "GhostPost". | |
| If you don't expect "page" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "page" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "page" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostPost". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostPost". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_styles" on type "GhostPost". | |
| If you don't expect "codeinjection_styles" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_styles" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_styles" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/post.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostTag". | |
| If you don't expect "feature_image" to exist on the type "GhostTag" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostTag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostTag". | |
| If you don't expect "description" to exist on the type "GhostTag" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostTag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostTag". | |
| If you don't expect "meta_title" to exist on the type "GhostTag" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostTag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostTag". | |
| If you don't expect "meta_description" to exist on the type "GhostTag" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostTag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_description" on type "GhostPost". | |
| If you don't expect "og_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_image" on type "GhostPost". | |
| If you don't expect "og_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "og_title" on type "GhostPost". | |
| If you don't expect "og_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "og_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "og_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_description" on type "GhostPost". | |
| If you don't expect "twitter_description" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_image" on type "GhostPost". | |
| If you don't expect "twitter_image" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "twitter_title" on type "GhostPost". | |
| If you don't expect "twitter_title" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "twitter_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "twitter_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostPrimary_tag". | |
| If you don't expect "description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostPrimary_tag". | |
| If you don't expect "feature_image" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_description" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostPrimary_tag". | |
| If you don't expect "meta_title" to exist on the type "GhostPostPrimary_tag" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostPrimary_tag": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "description" on type "GhostPostTags". | |
| If you don't expect "description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "feature_image" on type "GhostPostTags". | |
| If you don't expect "feature_image" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "feature_image" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "feature_image" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_description" on type "GhostPostTags". | |
| If you don't expect "meta_description" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_description" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_description" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "meta_title" on type "GhostPostTags". | |
| If you don't expect "meta_title" to exist on the type "GhostPostTags" it is most likely a typo. | |
| However, if you expect "meta_title" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "meta_title" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPostTags": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "canonical_url" on type "GhostPost". | |
| If you don't expect "canonical_url" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "canonical_url" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "canonical_url" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "page" on type "GhostPost". | |
| If you don't expect "page" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "page" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "page" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_foot" on type "GhostPost". | |
| If you don't expect "codeinjection_foot" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_foot" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_foot" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_head" on type "GhostPost". | |
| If you don't expect "codeinjection_head" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_head" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_head" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js | |
| There was an error in your GraphQL query: | |
| Cannot query field "codeinjection_styles" on type "GhostPost". | |
| If you don't expect "codeinjection_styles" to exist on the type "GhostPost" it is most likely a typo. | |
| However, if you expect "codeinjection_styles" to exist there are a couple of solutions to common problems: | |
| - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server | |
| - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have | |
| - You want to optionally use your field "codeinjection_styles" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") | |
| It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost": | |
| https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions | |
| File: /home/saif/Projects/gatsby-starter-ghost/src/templates/tag.js |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment