Local Storage cache is not auto-clearing about archive-website HOT 8 CLOSED

Curious how this could be achieved. Could we have a unique id number stashed with the localStorage cache that changes/increments with each release and bust the cache if it doesn't match?

from archive-website.

Can we use sessionStorage instead or use ESLint version as the namespace key?

from archive-website.

ESLint version as a key might be a good idea. That would make things easy, I think. sessionStorage wouldn't help, since the whole idea of the caching will be lost

from archive-website.

Yeah, I like that idea too! Might try to take a look at this later tonight

from archive-website.

I'm still not entirely clear on how the ESLint version gets updated for the site - is it a manual thing? Or is it pulled in somewhere and updated programmatically?

from archive-website.

I'm looking at that for #195. I think you have to run npm run browserify or make browserify or something from the main eslint repo. A bit of magic for sure. I believe there may some sort of automated way the site gets updated. @ilyavolodin will know for sure :)

from archive-website.

I hope "turn all rules off" button.

I'm using the demo after I turned all rules off.
I'm afraid that I must do that on every release...

from archive-website.

ESLint version gets updated from the main repository by running npm run browserify (or rather by running npm run minor/major/patch which will run npm run gensite which will run browserify task). npm run gensite will automatically update the site, but it will also pull all of the documentation from main repository, so not something you want to do when you just want to update demo page.

from archive-website.