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

Remove implicit leveldown #346

Merged
merged 4 commits into from
May 26, 2015
Merged

Remove implicit leveldown #346

merged 4 commits into from
May 26, 2015

Conversation

juliangruber
Copy link
Member

Implicit leveldown is based on two assumptions:

  • leveldown is the primary backend for levelup
  • people use levelup directly (instead of convenience packages like level)

I consider both not true any more, so it's time to clean up for v2.

This pull request is based on the remove/deprecated branch, since without implicit leveldown it's impossible to expose levelup.repair and levelup.destroy.

@juliangruber juliangruber added v2 cleanup Housekeeping labels May 26, 2015
@mcollina
Copy link
Member

+1
Il giorno mar 26 mag 2015 alle 19:41 Julian Gruber notifications@github.com
ha scritto:

Implicit leveldown is based on two assumptions:

  • leveldown is the primary backend for levelup
  • people use levelup directly (instead of convenience packages like
    level)

I consider both not true any more, so it's time to clean up for v2.

This pull request is based on the remove/deprecated branch, since without
implicit leveldown it's impossible to expose levelup.repair and

levelup.destroy.

You can view, comment on, or merge this pull request online at:

#346
Commit Summary

  • remove .approximateSize()
  • remove .destroy() and .repair()
  • remove optional leveldown
  • docs

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#346.

@ghost
Copy link

ghost commented May 26, 2015

This looks great! And we can remove all the path handling logic too that was clogging up the levelup(leveldown(...)) use-case (which should be the preferred use-case now).

@jcrugzz
Copy link
Contributor

jcrugzz commented May 26, 2015

+1. Seems like this will go hand in hand with open state being handled in leveldown?

@juliangruber
Copy link
Member Author

This looks great! And we can remove all the path handling logic too that was clogging up the levelup(leveldown(...)) use-case (which should be the preferred use-case now).

exactly, this is part of preparation for that. i have a julian-v2 branch https://github.com/Level/levelup/tree/julian-v2 that has that already implemented, and I'm going to try to put this into master for v2 one step at a time.

@juliangruber
Copy link
Member Author

+1. Seems like this will go hand in hand with open state being handled in leveldown?

yup! abstract-leveldown already got .status here, now we just need to figure out the sane way for levelup to use it

juliangruber added a commit that referenced this pull request May 26, 2015
@juliangruber juliangruber merged commit d04f864 into v2 May 26, 2015
@juliangruber juliangruber deleted the remove/implicit-leveldown branch May 26, 2015 20:46
@ralphtheninja
Copy link
Member

Good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Housekeeping
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants