Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

Docs and Reasons for the JWT API changes #637

Closed
HJFinch opened this issue Dec 5, 2017 · 2 comments
Closed

Docs and Reasons for the JWT API changes #637

HJFinch opened this issue Dec 5, 2017 · 2 comments
Labels
question

Comments

@HJFinch
Copy link

HJFinch commented Dec 5, 2017

Hey there,
I wanted to understand what the reasons behind the change in the jwt package were and how this should be used now?
Is there any recommendations on how to work with this (real examples?) as this kinda happened under the hood and I was a little surprised by it, after stuff looked different (or was not working anymore).

Cheers,
Finch
@peterbourgon
Copy link
Member

Changes since when? Here are a few tickets that caused API changes, with rationale: #562, #526.

@peterbourgon
Copy link
Member

@HJFinch Does that help? Any outstanding questions?

@go-kit go-kit locked and limited conversation to collaborators Jul 17, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peterbourgon @HJFinch