You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 default MemoryStore.
Thoughts?
Would you accept a PR implementing such feature?
The text was updated successfully, but these errors were encountered:
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: