Handle Deleting of Files Properly w/ GraphQL, etc

[bradennapier]

Description

If you delete or rename markdown pages right now you can not get rid of them and errors pop up even if you restart gatsby develop. Only way to fix it appears to be to delete everything and start over (.cache and public folders).

Perhaps cleaning the cache should be done in some way? It still thinks these posts exist many hours after they are completely removed.

I had assumed maybe there was a gatsby clean or gatsby purge but I didn't see it so it would appear this would break forever for anyone that did't know they had to manually delete those folders on every change?

Steps to reproduce

1. Make Markdown File in gatsby-advanced-starter but any should work as the gatsby node config doesnt re-run and/or runs in cache (dont know really with the magic that happens)

2. Delete it

3.It still exists on reloads in the graphql database

...

I get these errors because it is thinking a bunch of files exist when I simply renamed or deleted them.

[KyleAMathews]

Are you on the latest version of gatsby? I spent nearly a day on this very issue a few weeks ago :-)

[bradennapier]

I believe I am unless it came out like a day ago. Will be awesome if that is it - one moment.

[bradennapier]

Nope.. reinstalled gatsby completely and on version gatsby@1.9.222 and still the items are returned from graphql queries there is rendering and I deleted that file about 8 hours ago. Only fix is to delete .cache and public manually.

I will do that now though in case it will only handle from nwo on rathr than files I deleted previously.

[bradennapier]

oof - just noticed tons of errors - yall need a gatsby clean to clear the cache and public or something. Looks like updating versions made it break since it was reading cache which was now invalid?

[KyleAMathews]

Those errors are React errors... it's not necessarily something Gatsby is doing. I'll look at gatsby-advanced-starter and see if I can reproduce this really quick.

[KyleAMathews]

We aim towards the cache being 100% accurate. A cache you have to clean all the time is useless.

Would love it if you could help me figure out why this is happening so we can solve it!

[KyleAMathews]

I just installed the starter and ran yarn why gatsby and it said the version of Gatsby is 1.9.178 — which means it doesn't have any of the new fixes for handling deleting files.

Can you double-check what version you're on?

[KyleAMathews]

I'm upgrading packages now and then will test if I can make the cache invalid by deleting files.

[bradennapier]

I updated to the package shown in the post above. The errors were react but they were a result of the query returning data about files that no longer exist. Removed cache manually now and going to try more, unfortunately my ISP appears to be on the fritz.

[KyleAMathews]

I've replicated the bug — looking into why it's happening.

[bradennapier]

Great! Also happens when I move them into different folders as well. Seems it just needs to run a new query on the overall file contents when certain things occur.