You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression
[ ] Bug report
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
I used @nestjs/config to get the env is development or production
And used the @nestjs/sequelize to create the sequelize instance
It look like the document
I'm submitting a...
Current behavior
I used
@nestjs/config
to get the env is development or productionAnd used the
@nestjs/sequelize
to create the sequelize instanceIt look like the document
Expected behavior
I want to set the
sync: { force: false }
when the environment is 'production'and set
sync: { force: true }
when the environment is 'development'Minimal reproduction of the problem with instructions
null
What is the motivation / use case for changing the behavior?
null
Environment
Nest version: ^7.0.0
For Tooling issues:
Others:
@nestjs/sequelize: ^0.1.0,
@nestjs/config": ^0.5.0,
The text was updated successfully, but these errors were encountered: