Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement cache #22

Open
alexander-akait opened this issue Feb 2, 2017 · 5 comments
Open

Implement cache #22

alexander-akait opened this issue Feb 2, 2017 · 5 comments
Labels
🗄 area/interface This affects the public interface help wanted 🙏 This could use your insight or help 🧒 semver/minor This is backwards-compatible change 🦋 type/enhancement This is great to have 🙆 yes/confirmed This is confirmed and ready to be worked on

Comments

@alexander-akait
Copy link

That would be great, at the moment only eslint have cache, in stylelint we working at this stylelint/stylelint#2270 👍 Moved from remarkjs/remark-lint#120

@wooorm
Copy link
Member

wooorm commented Feb 2, 2017

👍

@wooorm
Copy link
Member

wooorm commented Feb 7, 2017

By the way, have you checked the --watch option with the CLI? That uses some caching!

@ChristianMurphy
Copy link
Member

It would also be nice if the cache strategy could be pluggable.
A linter's caching needs are different than a transformer's, etc.

@ChristianMurphy
Copy link
Member

Another possible approach could be storing the cache as part of a vFile abstraction, see vfile/ideas#2

@StarpTech
Copy link
Contributor

StarpTech commented Aug 28, 2018

Hi, what kind of cache are we talking about?
What's the issue here?

I use tools like https://github.com/azz/pretty-quick/blob/master/README.md to speed up the formatting process. I could imagine a simple package which pass a list of all changed files to unified (based on git)

@wooorm wooorm added help wanted 🙏 This could use your insight or help 🗄 area/interface This affects the public interface 🙆 yes/confirmed This is confirmed and ready to be worked on and removed needs pr labels Aug 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🗄 area/interface This affects the public interface help wanted 🙏 This could use your insight or help 🧒 semver/minor This is backwards-compatible change 🦋 type/enhancement This is great to have 🙆 yes/confirmed This is confirmed and ready to be worked on
Development

No branches or pull requests

4 participants