chec / gatsby-source-chec Goto Github PK

Instead of manually checking for the presence of a publicKey, we should migrate to the pluginOptionsSchema.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

When configuring the plugin it would make sense to name the token as publicKey as it's more explicit, and there's no need of a secretKey in this source plugin.

Generating pages for products would be a better fit for a theme or starter, and instead leave the source plugin to only source content and generate nodes.

The Chec API requires you to make a request to v1/products/:productId/variants to fetch the individual variants of products.

We should fetch this after fetching products, and connect them internally with Gatsby so you can query the variant data.

Depending on the API version people are using, we'll need to make sure we're conditionally trying to build nodes if they exist in the product node.

One of the great things about working with Gatsby is the ability to use gatsby-image library. To use this properly, we'll need to create local image nodes from the remote URL.

An example of this can be seen here: https://github.com/notrab/gatsby-source-transistorfm/blob/master/gatsby-source-transistorfm/gatsby-node.js#L44-L51

Currently axios is used to make API calls, however, we could instantiate a new @chec/commerce.js instance and use the helpers here to fetch resources.

This plugin crashes whenever sub categories are used. The dependencies are outdated and introduce 25 errors, 2 of them critical.

This issue provides visibility into Renovate updates and their statuses. Learn more

This repository currently has no open or pending branches.

• Check this box to trigger a request for Renovate to run again on this repository

Currently only the max returned products per page will be returned and nodes built.

If there are more pages, we should fetch them!

It would be useful to rename the package from gatsby-source-chec to gatsby-source-commercejs as it uses commerce.js under the hood to make API calls.

It would be useful to create Category nodes returned from the Chec API.

It would be useful to switch to yarn workspaces, and implement an example folder.

https://github.com/notrab/gatsby-source-transistorfm is a simple example of the setup required here.

We can reduce the overall code structure to live inside gatsby-node.js instead of separate files, since there isn't much going on under the hood anymore.