File dependency caching about vars HOT 3 OPEN

Just set cache to false when in development, it'll stop the cache being built. I was thinking about rebuilding the cache module anyway to do similar to what you were saying anyway.

https://github.com/m1/Vars#options

from vars.

@francislavoie okay to close this?

from vars.

Sorry I never answered, I still think this is needed. There needs to be a good way to invalidate the cache. You said you were thinking about rebuilding the cache module, so I think it's worth keeping this issue open until you get to that.

I was thinking about writing a PR for this, but right now there's no obvious way to get a list of the files loaded from the cache module. It would need a bit of a rewrite to make that information available, and that's more work than I have time to commit.

Your suggestion for development is fine, but I don't just want this for development, I want it for production too so I don't have to wipe the cache (delete the vars folder) or wait 5 minutes. I also use a long-running job queue service, and if the config is changed I need to reboot those as well (they only read config once at the start) and if the old config is cached and I reboot them, then they'll still have the old config. So I always have to wipe the cache myself every time I make a change.

For now, I'm going to write a manual check ahead of where I load M1\Vars\Vars where I do filemtime against the cache and my config file, if the config is newer I'll unlink the cache file.

Thanks!

from vars.