Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR #85923 GRAPHQL on tuidoc #5

Open
st-schneider opened this issue Mar 29, 2020 · 13 comments
Open

ERROR #85923 GRAPHQL on tuidoc #5

st-schneider opened this issue Mar 29, 2020 · 13 comments
Labels

Comments

@st-schneider
Copy link

Describe the bug

> gatsby build --prefix-paths "latest"

success open and validate gatsby-configs - 0.026s
success load plugins - 0.302s
success onPreInit - 0.004s
success delete html and css files from previous builds - 0.010s
success initialize cache - 0.006s
success copy gatsby files - 0.051s
success onPreBootstrap - 0.009s
success createSchemaCustomization - 0.015s
success source and transform nodes - 0.085s
success building schema - 0.215s

 ERROR #85923  GRAPHQL

There was an error in your GraphQL query:

Cannot query field "allNavigationJson" on type "Query".

If you don't expect "allNavigationJson" to exist on the type "Query" it is most likely a typo.
However, if you expect "allNavigationJson" 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 "allNavigationJson" 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: gatsby-node.js:26:10

not finished createPages - 0.025s```

## To Reproduce
Steps to reproduce the behavior:
1. Make a simple tuidoc.config.json
2. run tuidoc

## Expected behavior
Work.

## Desktop (please complete the following information):
 - OS: Mac OS
@seonim-ryu
Copy link
Member

@bm-stschneider When I think, the reason for this error seems to be the problem that the JSDoc data you wrote is missing or not parsed correctly.

Cannot query field "allNavigationJson" on type "Query".

Could you show me the JSDoc you wrote?

@st-schneider
Copy link
Author

The thing is, I don't know where this happens since there is no reference to a file or so.

@lunadev55
Copy link

Any progress in fixing this issue ? having the same problem here, unfortunately :(

@cybertricksnet
Copy link

SAME HERE 👍

@juicycool92
Copy link

same here, hopefully fix it soon ;_;

@rasimack
Copy link

Same here when fetching data from strapi hosted in Google cloud, anyone found a solutions?

@seonim-ryu
Copy link
Member

@bm-stschneider @lunadev55 @realmrsyd @juicycool92 @rasimack
First, I need the following information to confirm this situation. The tuidoc.config.json file information you are using and the javascript file using JSDoc.

There was an error in your GraphQL query:
Cannot query field "allNavigationJson" on type "Query".

This error occurs when JSDoc cannot be parsed properly and creates an LNB component of @toast-ui/doc. Anyone is good, so give me some information.

@kwangheum
Copy link

나도 이거 떠서 찾아왔는데.. 해결 안된건가요..?
JSDoc 사용하다가 demo랑 같이 사용하려고 했는데 저 오류가 뜨네요..

{
  "header": {
    "logo": {
      "src":"/doc-resources/logo.png",
      "title":{
        "text":"gg"
      },
      "version":true
    }
  },
  "main": {
    "filePath": "README.md"
  },
  "api": {
    "filePath":"./src/",
    "permalink":false
  }
}

이렇게 입니다...

@vaniadimova
Copy link

vaniadimova commented Sep 18, 2020

I think it has a lot to do with plugins versions when I used the specific ones given by the site I HAD NO ISSUE, when I just uploaded the plugins with no @2.20.0 (per se) then I got the error, hope I am right. Or I had a typo, all good now.

@swtalk
Copy link

swtalk commented Sep 18, 2020 via email

@HarmoGlace
Copy link

I have the same error

@swtalk
Copy link

swtalk commented Oct 30, 2020 via email

@MacroMan
Copy link

I had this error too, but I fixed it. Hope this helps some facing this error.

My api.permalink setting was invalid. I turned it off by setting to false and no more error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests