-
-
Notifications
You must be signed in to change notification settings - Fork 407
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:security:form-login] no interaction for make:security:form-login #1595
base: main
Are you sure you want to change the base?
Conversation
c7c8f6a
to
9529eda
Compare
9529eda
to
46c1f55
Compare
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.
A couple of comments and we can get this moving...
src/Maker/Security/MakeFormLogin.php
Outdated
private string $controllerName; | ||
private string $firewallToUpdate; | ||
private string $userClass; | ||
private string $userNameField; | ||
private bool $willLogout; |
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.
We need to keep both of these properties. MakerBundle is getting away from "abusing" setArgument
and getArgument
for the purposes of passing user input from one method to the next within a maker command. e.g. separation of concerns.
tl;dr interact()
configures and sets any values onto their respective properties that will later be needed in generate()
interact()
should get, validate, and set input.
generate()
should only use values that are set via class properties when possible.
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.
ok so we don't have to use --no-interaction option for all makers ?
allow command make:security:form-login with name in argument to no interaction
as help says : make:security:form-login [<controllerName>]