-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Proofread jwt #334
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
Proofread jwt #334
Conversation
It is/should be? |
02269f4
to
0670765
Compare
I'm not sure I get your question(s?)
No, far from it, there does not seem to be a limit at all.
If you want easier diffs, probably. |
0670765
to
1f4ec32
Compare
github helps a lot with the word highlight though |
yes haha, and I thought we had a limit |
We have a limit, but we don't enforce it to not annoy the contributors... Maybe should we add a check for that and some guidance on how to fix it automatically. |
core/jwt.md
Outdated
|
||
 | ||
|
||
### Adding a New API Key | ||
|
||
All you have to do is to configure the API key in the value field. | ||
By default [only the authorization header mode is enabled](https://github.com/lexik/LexikJWTAuthenticationBundle/blob/master/Resources/doc/index.md#2-use-the-token) in [LexikJWTAuthenticationBundle](https://github.com/lexik/LexikJWTAuthenticationBundle). | ||
All you have to do is configure the API key in the `value` field. |
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.
configuring?
Thanks @greg0ire |
The diff would be easier to read if you capped lines to some limit (120 chars?). Consider it.