-
Notifications
You must be signed in to change notification settings - Fork 8
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
Compatible arangojs versions? #8
Comments
when modifying the store object to match the documentation I now get a connection issue. I made a ticket with Arangojs here: arangodb/arangojs#758 but it only happens when using ArangoStore. |
The package was recently updated according to one of the forks that people had been using. I am no longer maintaining this package so I trusted the fork (according to the author which told me it worked fine) and updated this package. If it is no longer working for you, please downgrade to the previous version, or create a pull request to fix it. |
@cjarv seems to be working fine for me with the latest |
Hello all,
I just did a fresh npm install to find that this package is now conflicting with arangojs in the Database class in the else of the constructor. It seems that the name of the database is passed where it is expecting the url, then throws a "request has no protocol error" because it just has the name of the db (arangojs: database.js>line 92). This package was working perfectly fine a few months ago but would like to know if there is a patch for this? Also when setting up the ArangoStore object as shown in the example it never worked however when setting it up as shown in one of your help tickets it has always worked in the past. Thanks for your help!
Cheers,
cjarv
The text was updated successfully, but these errors were encountered: