-
Notifications
You must be signed in to change notification settings - Fork 121
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
symfony/lock required in non-dev #104
Conversation
Could you please update doc accordingly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the lock should remain in require-dev, but do a check before using the feature to be able to throw an exception to warn the user to add it on dependencies
@maxhelias i would only agree on keeping it in require-dev if it wasn't required for the first installation steps. As it's now possible again to use default doctrine commands to update the database the docs could be changed to use those. Then we could mention the symfony/lock install when describing multi-db setups or cleaning up old logs. @DamienHarper how would you like to handle this? |
0b3c038
to
dcd4439
Compare
@maxhelias this is already the case and documented in the cleaning section of the documentation (only) as of now. In order to keep dependencies minimal and given the fact that (AFAIK):
So, we don't need to make this dependency a hard requirement => let's keep it in |
0a56048
to
9ede526
Compare
@DamienHarper i changed the file so it's supporting |
Prevent users with an exception at the beginning of the execution command like this : if (!class_exists(Lock::class)) {
throw new LogicException('The Lock component is required to use this command. Try running "composer require symfony/lock".');
} Is a must have in addition to the documentation |
@maxhelias this is already enforced by using the LockableTrait |
Indeed, I had not seen 👍 |
@n3o77 we only miss the notice in the doc to merge this PR |
@DamienHarper sorry, i thought you already changed that. I'll update in a few min |
beeaa7c
to
fb43d48
Compare
I moved the |
otherwise
audit:clean
andaudit:schema:update
can’t be executed