Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Private Migrations have broken default names. #327

Closed
mattpolzin opened this issue Jun 13, 2020 · 0 comments · Fixed by #328
Closed

Private Migrations have broken default names. #327

mattpolzin opened this issue Jun 13, 2020 · 0 comments · Fixed by #328
Assignees
@mattpolzin
Labels
bug Something isn't working

Comments

@mattpolzin
Copy link
Member

A Migration in a private context will have a name component like (unknown context at $10fad3264) that will change from one execution to the next causing big problems. Names of migrations MUST be stable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattpolzin mattpolzin

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Disallows private-scoped migrations with default names. vapor/fluent-kit
1 participant
@mattpolzin