-
Notifications
You must be signed in to change notification settings - Fork 2
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: dbMigrationPathOpt - add db migration path to MapeoProject
and MapeoManager
#384
Conversation
* add optional opt for projectMigrationFolder to mapeoProject with default value * add optional opt for projectMigrationFolder and clientMigrationFolder to mapeoManager with default values Since I put a default value to both params I made both of them optionals, but maybe it not the right approach? Also the types for both are strings and then turned into a path with `new URL`
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.
I don't think the options should be optional with a default value, as it assumes the location of the migrations directory, which is what we're trying to avoid with this change. Will need to update/fix the tests to account for the suggested changes.
Also suggested changing migration
to migrations
(plural) to be consistent with the option name from drizzle
Co-authored-by: Andrew Chou <[email protected]>
Co-authored-by: Andrew Chou <[email protected]>
Co-authored-by: Andrew Chou <[email protected]>
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.
nice!
Should close #341
For now:
Since I put a default value to both params I made both of them optionals, but maybe it not the right approach?
Also the types for both are strings and then turned into a path with
new URL