newrelic / opensource-website

Source code for New Relic's Opensource site.
https://opensource.newrelic.com
Apache License 2.0
155 stars 89 forks source link

chore: updated component guide & fix main build #903

Closed jpvajda closed 2 years ago

jpvajda commented 2 years ago

This PR explains the github sponsors component as it's custom to this site.

jpvajda commented 2 years ago

There are actually 2 bugs that seemed to be related to this component that we should fix

https://github.com/newrelic/opensource-website/issues/901 https://github.com/newrelic/opensource-website/issues/902

gatsby-cloud[bot] commented 2 years ago

Gatsby Cloud Build Report

:triangular_flag_on_post: Your build failed. See the build logs here

Errors

There was an error in your GraphQL query:

Cannot query field "nodes" on type "GithubDataRawResultDataOrganizationSponsoring".

If you don't expect "nodes" to exist on the type "GithubDataRawResultDataOrganizationSponsoring" it is most likely a typo.
However, if you expect "nodes" 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 "nodes" 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 at 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 "GithubDataRawResultDataOrganizationSponsoring":
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/schema-customization#creating-type-definitions
jpvajda commented 2 years ago

the failing build issue is captured in this issue: https://github.com/newrelic/opensource-website/issues/901

jpvajda commented 2 years ago

closing as the decision is to remove this component as we aren't sponsoring projects at the moment.