-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
rocks-level implementation #121
Comments
I have made some good progress but I'm mostly developing for our in-house needs which might not work well for an open-source project. I would recommend you fork mine and continue from there. |
It should be fully compatible with abstract-level. Mostly the development style that doesn't fit well with a open-source type package. |
A better starting point is |
Yea... classic-level as a base didn't work for me and upstreaming changes was too slow. Another option would be to apply the "improvements" I've made to classic-level and then forking that into a rocks-level. |
@ronag The leveldown-as-a-base strategy has worked well for several years on @MeirionHughes TLDR, you can use ronag's |
Yes, didn't mean it as criticism. It just didn't work for me. I think your suggestion is better community-wise. |
Just checking to see if anyone has started rocks-level privately before I have a stab? I see @nxtedition @ronag https://github.com/nxtedition/rocks-level seems to have updated their fork to abstract-level, but their fork is significantly ahead (~700 commits).
The text was updated successfully, but these errors were encountered: