-
Notifications
You must be signed in to change notification settings - Fork 19
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
Json settings file #9
Comments
Can you provide examples of naming conventions? |
First project: Migration files are in Migrations/DefaultDB/ directory with names like DefaultDB_yyyyMMdd_HHmmss_description.cs I know that I can change projects and move files to Migrations directory like fluent-migrator generator uses. Now I see that here in gitlab is newer version than in nuget.org. This version has more useful parameters in command line. Can you please publish new version to nuget.org? Anyway some .json settings file per project would be useful instead of typing constants to command line for each new migration. |
I can try to get to this next week. /cc @kendaleiv can probably hook this up to our CI/CD pipeline. |
CI/CD added in #10. |
Would be great to have posibilty to add parameters for new migration file. Or maybe better would be to have json settings file in project. I need different naming conventions in different projects.
The text was updated successfully, but these errors were encountered: