-
Notifications
You must be signed in to change notification settings - Fork 5
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
Can we do ready()
implicitly?
#2
Comments
only-cliches
pushed a commit
that referenced
this issue
Aug 14, 2019
This feature will be live in version |
Thank you very much for your improvement! It will help me to solve my problems inside my library, cheers! |
This was referenced Aug 14, 2019
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I understand that we need some initialization tasks before the db will be ready to use, so the code in the
ready()
is necessary.However, the current design will force the user to call
ready()
before using the SnapDb, which I believe can be done inside the library itself.I will get wrong with the following code:
I would love to get it to work without the
ready()
call.The text was updated successfully, but these errors were encountered: