-
Notifications
You must be signed in to change notification settings - Fork 161
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
Status resolve/reject #282
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The handling of 400 level statusCodes via error callback or reject is not backward compatible after 9.0.1 (due to changes in axios somewhere around 0.21.1)
Expected Behavior
In the following code example, if a database does not exist when using nano 9.0.1 or earlier,
exists
would be true ifmissing_db
does not exist:Current Behavior
The above example code rejects with
err
as:Possible Solution
The following change to the config object corrects the issue, as a workaround:
Steps to Reproduce (for bugs)
missing_db
does not existContext
It is necessary to be able to know if a database exists or not
Your Environment
The text was updated successfully, but these errors were encountered: