-
-
Notifications
You must be signed in to change notification settings - Fork 527
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
Support for Improved Migration Directory Structure and Configuration #1349
Labels
Comments
The first two points are planned for the CLI/sequelize-auto rewrite. I'll leave this issue open so we do not forget about it when we work on more of a roadmap for the rewrite |
Migrations are run in a deterministic order based on the name of the file. If we support nested folders or multiple sources of migration files, then that order becomes difficult to understand and easy to break. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
I would like to propose a feature enhancement to support a more flexible and organized migration directory structure in Sequelize, along with improvements in the configuration setup. The current options of using
config.js
,.sequelizerc
, andconfig.json
provide a basic setup but lack the ability to handle complex directory structures and additional migration sources.Feature Requests:
Sample Directory Structure:
Additional migration sources: Allow the specification of multiple migration sources outside the default migrations folder. This would provide flexibility to manage migrations across different directories, enabling better separation of concerns for microservices or modules.
Clear documentation and examples: Enhance the documentation with clear examples and use cases to guide users in setting up and utilizing the advanced migration directory structure and configuration options effectively.
Expected Benefits:
I believe these enhancements would greatly benefit developers working with Sequelize and enhance the overall migration management experience.
The text was updated successfully, but these errors were encountered: