-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
bug(gatsby-transformer-documentationjs): plugin causes error when no documentationJS nodes are found #24592
Comments
@tesseralis I think you have a typo |
Is anyone working on this? |
@tesseralis can I work on it? |
@mikeattara are you still interested in working on this? |
@tesseralis yes |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Description
gatsby-transformer-documentationjs
fails when no documentation nodes are defined.Steps to reproduce
gatsby-transformer-documentationjs
plugindocumentationJS
, eg:Expected result
The
allDocumentationJS
query returns an empty arrayActual result
Build fails with
Type with name "DocumentationJSComponentDescription" does not exists
Proposed solution
Add a
type DocumentationJSComponentDescription
with the appropriate fields to the gatsby-node of the plugin: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-transformer-documentationjs/src/gatsby-node.js#L47Environment
N/A
The text was updated successfully, but these errors were encountered: