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
Allow to provide custom store management engines. #583
Comments
Thank you for the request, will try to add new way to add stores |
Thanks, don't hesitate to take my offer of providing this feature myself if you want :) Btw, i think it will be good turning the close() method async as well, so that stores may does decide to flush to disk at that stage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the only provided stores are memory and leveldb which are not extensible, and developing new ones requires those to be published under this repository maintenance.
jscpd/packages/jscpd/src/init/store.ts
Line 7 in 1fc5099
I would like to suggest the ability to provide a custom-made store engine, similar to the way eslint-plugin-local-rules does work.
i.e. my idea is that through the
--store
command line option (and/or config file) we can provide a path to a JS file to be loaded and used as store, overriding the defaultMemoryStore
.Thoughts?
Would you accept a PR implementing such feature?
The text was updated successfully, but these errors were encountered: