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

Expose Sequelize lib #6

Closed
ekryski opened this issue Dec 28, 2015 · 2 comments
Closed

Expose Sequelize lib #6

ekryski opened this issue Dec 28, 2015 · 2 comments

Comments

@ekryski
Copy link
Member

ekryski commented Dec 28, 2015

So that end users don't need to require it separately we should just expose the underlying sequelize lib. Just in case people need access to it.

@daffl
Copy link
Member

daffl commented Dec 29, 2015

I don't think this is necessary (or even possible). You only have to supply the initialized model. The plugin itself doesn't directly depend on Sequelize at all.

@ekryski
Copy link
Member Author

ekryski commented Dec 29, 2015

Right. Sequelize gets initialized outside of the adapter.

@ekryski ekryski closed this as completed Dec 29, 2015
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

No branches or pull requests

2 participants