[8.0] Migrations files should be no longer loaded in packages #33495
Unanswered
DarkGhostHunter
asked this question in
General
Replies: 1 comment 2 replies
-
I don't think we should do this. We've been using package shipped migrations just fine for years (like in Passport). Exporting the migrations and modifying is actually the thing that should be discouraged imo. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm having a tantrum here, but I want to put here a bug that has been plaguing me since 5.0.
Basically, when a migration is included in a package, it will be loaded without any problem. But if the user publishes the migration into their
database/migrations
, next time it runmigrate
, PHP will halt saying:Having packages load migrations should be discouraged, so users can publish the migration manually and adjust them to their needs.
For this, I think Laravel 8.0 should discourage migration files, and rather, add
publishMigrations
helper to the service provider to allow clean migrations procedures, using thedatabase/migrations
path as default.The above is just syntax sugar to publish the files under the
migrations
tags.Beta Was this translation helpful? Give feedback.
All reactions