-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[10.x] Remove autoload dumping from make:migration #46215
Conversation
60f8152
to
61ca9dc
Compare
0df45b3
to
3f03d3f
Compare
You could remove the |
@timacdonald the |
@taylorotwell I thought the same thing when I set out on this journey, however class based migrations are no longer supported - unless I am missing something. Using the following script will:
Running any of the following you should see that
It seems this functionality was removed in
Same deal. |
@ankurk91 I didn't remove the dependency as I thought a user-land class may be extending these and potentially interacting with the I might deprecate it, though 💡 |
This PR removes the
composer dump
call when making a migration files. Dumping the autoloader adds a very noticeable (an frustrating) delay and adds no benefit as generated migrations are now all "require" based.The
make:migration
command is no longer capable of generating class based migrations (it doesn't replace{{ class }}
anymore, so we don't even need to do any checks.I've left the composer dependency on the classes even though they are no longer used.
Delay example on a fresh project
Screen.Recording.2023-02-21.at.7.00.22.pm.mov
After this change
Screen.Recording.2023-02-22.at.10.46.29.am.mov