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

Product object not showing in the graphQL #74

Open
airjoshb opened this issue Nov 9, 2022 · 3 comments
Open

Product object not showing in the graphQL #74

airjoshb opened this issue Nov 9, 2022 · 3 comments
Assignees
Labels

Comments

@airjoshb
Copy link

airjoshb commented Nov 9, 2022

Prerequisites

[ x ] Put an X between the brackets on this line if you have done all of the following:

  • Read through the README fully.
  • Ensured you are running Node v.10 or above.
  • Made sure you're using at least Gatsby v.2.0.15.
  • Checked that your issue isn't already filed.

Describe the bug
The "Product" object is not showing up. I can add other objects, such as "Price" and "Customer" and they show up in the graphQL, but Product does not. I can get to products through the price object, but it does not have all of the attributes of the product that I need to display.

To Reproduce
Steps to reproduce the behavior:

  1. add the product object to gatsby-config.js
  2. restart
  3. check graphQL

Expected behavior
I would expect to see the allStripeProduct in the graphQL

Screenshots
Screenshot 2022-11-08 at 8 36 49 PM

Versions (please complete the following information):

os: Mac OS 13.0
node: v18.6.0
npm: 8.13.2
gatsby: 4.5.4
gatsby-source-stripe: 4.0.0

Gatsby config:

'gatsby-plugin-netlify',
    {
      resolve: `gatsby-source-stripe`,
      options: {
        objects: ['Price', 'Product', 'Customer'],
        secretKey: process.env.STRIPE_SECRET_KEY,
        downloadFiles: false,
      },
    },
@jansengunderson
Copy link

Also encountering this bug with Gatsby v5. Any updates on fixes?

@njosefbeck
Copy link
Owner

Hello! I no longer have time to maintain this package, so if someone wants to fork, create a fix, and submit a PR I can take a look and get it deployed. Thanks!

@brianfeister
Copy link
Collaborator

@airjoshb @jansengunderson open to helping own this, but question for @njosefbeck would you be willing to give other folks access / ownership so they can publish to npm without having to repeat that infrastructure setup work and keep the same npm package name?

I bumped into this library being unmaintained via need for newer stripe sdk version: #75

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

4 participants