Skip to content
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

#385: Tweak README #408

Merged
merged 2 commits into from
Oct 9, 2017
Merged

#385: Tweak README #408

merged 2 commits into from
Oct 9, 2017

Conversation

joovel
Copy link
Contributor

@joovel joovel commented Sep 27, 2017

Fixes issue #385 , adds a few other definite articles for clarity.

README.md Outdated
@@ -106,7 +106,7 @@ jwt.sign({

### jwt.verify(token, secretOrPublicKey, [options, callback])

(Asynchronous) If a callback is supplied, function acts asynchronously. Callback is passed the decoded payload if the signature and optional expiration, audience, or issuer are valid. If not, it will be passed the error.
(Asynchronous) If a callback is supplied, function acts asynchronously. The callback is passed the decoded payload if the signature is valid and optional expiration, audience, or issuer are valid. If not, it will be passed the error.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good change, however, this sentence always feels weird to me, don't you think it should use the same "pattern" as we use for sign?
The callback is called with the decoded payload... . If not, it will be called with the error.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated. I also made the wording between the Synchronous and Asynchronous section the same.

@ziluvatar ziluvatar merged commit d3f996b into auth0:master Oct 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants