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

Fix custom config path not being resolved #4

Merged

Conversation

ruimarinho
Copy link

The config path will now be resolved relative to process.cwd().

The config path will now be resolved relative to process.cwd().
@sdepold
Copy link
Member

sdepold commented Jun 3, 2014

I wonder if this could need a test ?

@ruimarinho
Copy link
Author

Yes, it definitely needs one. I tried but I found it quite hard to add new tests. I think I'm going to need assistance :-)

@sdepold
Copy link
Member

sdepold commented Jun 12, 2014

Hey :) I just merged my test refactoring and wonder if it is now easier for you to add some

@sdepold
Copy link
Member

sdepold commented Jun 13, 2014

guess i will write the test on my own and you could check them out afterwards and probably get an idea of how to write them in future PRs.

@sdepold
Copy link
Member

sdepold commented Jun 13, 2014

Excellent pick btw. I had tests for that but they were stupid :D

@sdepold sdepold merged commit 15a728a into sequelize:master Jun 13, 2014
@ruimarinho ruimarinho deleted the bugfix/resolve-custom-config-path branch June 23, 2014 16:11
@ruimarinho
Copy link
Author

Will do! Thanks for adding the tests!

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

Successfully merging this pull request may close these issues.

None yet

2 participants