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

Harmonising capitalisation of "token" in error strings #97

Merged
merged 1 commit into from
Aug 29, 2021
Merged

Harmonising capitalisation of "token" in error strings #97

merged 1 commit into from
Aug 29, 2021

Conversation

yoogoc
Copy link
Contributor

@yoogoc yoogoc commented Aug 29, 2021

No description provided.

@@ -61,7 +61,7 @@ func (c RegisteredClaims) Valid() error {
}

if !c.VerifyIssuedAt(now, false) {
vErr.Inner = fmt.Errorf("Token used before issued")
vErr.Inner = fmt.Errorf("token used before issued")
Copy link
Member

Choose a reason for hiding this comment

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

Curious, why this PR? Are you relying on the capitilization?

I'm indifferent about this one way or the other, but I'd prefer to avoid these kinds of PRs. Closing.

Also. https://github.com/golang/go/wiki/CodeReviewComments#error-strings

Copy link
Collaborator

Choose a reason for hiding this comment

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

Didn't he try to remove the capitalisation? It seems that we missed this one, the other Errorf calls are also lowercased.

Copy link
Member

Choose a reason for hiding this comment

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

Oops, diff'd it wrong. You're right, apologies @yoogoc . Thanks for your contribution. My mistake.

@mfridman mfridman closed this Aug 29, 2021
@mfridman mfridman reopened this Aug 29, 2021
@oxisto oxisto changed the title error msg Token to token Harmonising capitalisation of "token" in error strings Aug 29, 2021
@oxisto oxisto merged commit 3f50a78 into golang-jwt:main Aug 29, 2021
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