-
Notifications
You must be signed in to change notification settings - Fork 63
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
make:migration fails with default setup #205
Comments
Hello, Same result with Symfony 4.4 Interestingly, there is a warning message about the command make:reset-password does'nt find
then
Forced autowire :
When trying to add the config, the symfonycasts_reset_password namespace is not available for yaml config
|
I solved it
May the issue #133 helps you, I found a problem in composer installation of plugin symfony/flex. After check the project structure with official doc https://symfony.com/doc/current/setup/flex.html Run And run It successfully created file and at this point, |
Hm. Running the
I may try the whole thing over from scratch in a new branch shortly. :-( |
Howdy @Crell - sounds like the reset password config is missing.. do you have a # config/packages/reset_password.yaml
symfonycasts_reset_password:
request_password_repository: App\Repository\ResetPasswordRequestRepository |
That file wasn't created originally; and when I created it by hand before it didn't do anything. However, I then started over from scratch with a new branch, and that file was created by the setup script. I do not know why it was different, but that did resolve that issue. So, I guess I can close this. Thanks. |
I am following through the recommended setup from the README, but running into issues. Specifically:
bin/console make:reset-password
Walks through the wizard just fine, no error. At the end, it says to run
bin/console make:migration
However, doing so results in this error:
Which suggests that the services are not being autowired correctly. I added the following to
services.yaml
:Then running
make:migration
again results in:Yet that class does indeed exist.
At this point I figure there's something more wrong, so I put out a call for help. :-)
Running Symfony 5.4 on PHP 8.1.
The text was updated successfully, but these errors were encountered: