-
Notifications
You must be signed in to change notification settings - Fork 3
Conversation
Closes #1 |
fd1f396
to
06ff77a
Compare
f2e9c51
to
a21399a
Compare
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.
Hmm there are some changes needed here that I missed in the previous PR in Pinner. We should backport those changes to Pinner as well!
Also, I believe that this PR should contain the first migration that will bootstrap the DB into the current state!
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
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.
LGTM! But maybe I would wait with merge until the release/mainnet
is done and then regenerated the initial migration and start versioning DB after that 🤔
add db-migration command to cli
add initial db migration
exit process if migration require in sequelize init
df48cc0
to
b9dc0a0
Compare
run migration instead of sync
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
# Conflicts: # src/cli/precache.ts # src/sequelize.ts # src/utils.ts
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.
LGTM!
add db-migration command to cli