Add auto migration #86
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
So can we let bun handel the migration part related logic, instead of we doing it? |
main.go
Outdated
| @@ -18,6 +18,13 @@ func main() { | |||
| os.Exit(1) | |||
| } | |||
|
|
|||
| migrationsDir := "./migrations" | |||
There was a problem hiding this comment.
We were going to remove the ./migrations and use cmd/migrations, as we were going to let bun handle it?
For versioning and other feature?
|
Since this is been done in other PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Ticket Number
Description
In this Pr added a function to apply migration when a server start
Breaking Changes
If your feature introduces breaking changes or if something is missing, please mention the related issue tickets.
Development Tested?
Confirm whether the changes have been tested locally during development.
Tested in Staging?
Indicate whether the changes have been tested in the staging environment for dev to main.
Database Changes
Indicate whether the changes include modifications to the database.
Screenshots
Attach any relevant screenshots, such as test coverage reports, before and after images, or other visual aids.
Additional Notes
Include any additional notes, considerations, or explanations that might be helpful for reviewers.