Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
[Security]make:security:custom#19809
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:6.4
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Since MakerBundle `v1.59.0` - you can call `make:security:custom` to generate a simple, no-frills, custom authenticator based off the example in the docs.
| cases, you can use the ``make:security:custom`` command to create your own | ||
| authenticator. |
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.
Hmm.. we reference themake:* command in the doctrine section like I have here.. But we use thecode-block "syntax" else where in the doc's..
Line 727 inf7225d9
| ..code-block::terminal |
Sidenote - I should probably change the
Line 96 inf7225d9
| You can use the ``make:entity`` command to create this class and any fields you |
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.
Yes, I think theterminal code block would be better because it stands out a lot and it's easier to scan fore readers. Thanks!
Uh oh!
There was an error while loading.Please reload this page.
Since MakerBundle
v1.59.0- you can callmake:security:customto generate a simple, no-frills, custom authenticator based off the example in the docs.v1.59.0(Not yet released)