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
feat: deprecate accessing DataTypes directly on Sequelize class #14373
Conversation
Maybe I missed it with my quick scroll through the changes, but do we test somewhere that |
Not directly but |
Ah of course, that's true |
Nice changes, remove confusion between using |
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.
Can we mark this as breaking change in the commit message somehow?
Good change overall
Oh. Too slow :( |
Aha! There is a pr for this. |
To document this change? Yeah, this is indeed something that we needed to put in the upgrade guide EDIT: sequelize/website#80 |
🎉 This PR is included in version 7.0.0-alpha.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
* document deprecations & removals * document PR sequelize/sequelize#14373 Co-authored-by: Sascha Depold <sdepold@users.noreply.github.com>
…elize#14373) * feat: deprecate accessing DataTypes directly on Sequelize class * docs: update datatypes in jsdoc * test: revert fixing of a datatype that needs to be broken Co-authored-by: Rik Smale <13023439+WikiRik@users.noreply.github.com>
* document deprecations & removals * document PR sequelize/sequelize#14373 Co-authored-by: Sascha Depold <sdepold@users.noreply.github.com>
Pull Request Checklist
yarn test
oryarn test-DIALECT
pass with this change (including linting)?Description Of Change
This PR deprecates accessing DataTypes directly on the Sequelize constructor.
Instead, users should use the
DataTypes
object.These DataTypes take up a lot of possible names and should be kept in their own namespace: