Deleted Contentful post still present in local build about gatsby-starter-gcn HOT 6 CLOSED

Have you tried deleting the cache folder?

from gatsby-starter-gcn.

Many thanks for the information and tips.

10/10 would GitHub again.

from gatsby-starter-gcn.

Thanks @brandonkal - that seems to have done the trick!

I actually saw that as a potential fix for a similar issue on another project / rep, but a lot of people said it didn't work so I didn't bother trying it. That'll teach me...

Any idea why this may have happened? Any thoughts on how to prevent this from happening?

Wondering whether the cache can be deleted every time as part of the build process (or does this defeat the point of it in the first place?)...

from gatsby-starter-gcn.

The cache is useful for preventing unnecessary API calls to Contentful as usually changing posts or just adding more posts if more common. If you do delete content that has been built, deleting the cache is a nice way to avoid these problems.

from gatsby-starter-gcn.

OK thanks.

You've provided a solution, but I guess the root cause of the issue still exists. In this instance, would you close this issue on GitHub or leave it open for further investigation?

from gatsby-starter-gcn.

I would close the issue here as it is not related to the GCN starter project. This issue is related to the gatsby-source-contentful package not invalidating the cache when content is deleted. This package is maintained by gatsby.

It looks like there is already an issue open for this, and you can add to the discussion here: gatsbyjs/gatsby#3495

from gatsby-starter-gcn.