-
Notifications
You must be signed in to change notification settings - Fork 32
Compatibility with Sails v1 #36
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
base: master
Are you sure you want to change the base?
Compatibility with Sails v1 #36
Conversation
|
Old PR is a year old, I've written the changes requested plus some comments/docs/error improvements. |
lib/sailsDbMigrate.js
Outdated
| connection = sailsConfig.connections[connectionName] | ||
| } else if (sailsConfig.datastores) { | ||
| // v1.x.x | ||
| sailsConfig.datastores[connectionName] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
connection = sailsConfig.datastores[connectionName]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, missed that after transforming it from the nested ternary operator.
Fixed in fa2506a
|
I'm not using Sails any more. @booyokkk (or any other users of this lib), can I get a 👍 on this PR before I merge it? |
|
@leedm777 can this PR be merged to master? I had the same compatibility issue with Sails v1 while creating migrations. Though I found the solution but since it already has an open PR, it would be convenient if we can have this PR merged since it has not conflicts with master. |
this will fix issue building5#36
|
Please ignore this pull request. |
connectionordatastoreoption in configuration (to match sails v1 namings)