You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking through the code and logging the intermediate results of the plugins, the mdx navigation is correct but it fails somehow to add menus in GraphQL.
It sometimes appear after a refresh and after updating one key in a frontmatter, but I have not been able to reproduce this behavior every time.
in GraphQL, the navigation appears correctly in SitePageContext however.
I need to understand more how the nodes are created but in the createNode function of this plugin, the menu is correct (using some console.log and checking the results) and it is registered in GraphQL (using the function getAllNodes from Gatsby) via the plugin but somehow it is not displayed in the GraphQL after the plugin has been executed.
I've found that the menus node becomes available in GraphQL only after saving an .mdx document with the local development server already running. Upon initial npm run start it is missing, then saving any .mdx file results in the node appearing. Seems like maybe the plugin is missing some logic to execute when initially starting the dev server?
The
menus
GraphQL operation doesn't appear once I enable this plugin in a website using gatsby-plugin-mdx.Do I need to configure it somehow?
The text was updated successfully, but these errors were encountered: