-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
Fix deprecation notes #295
Conversation
Having the exact same interface as v4.0 to sign tokens. An interesting side-effect is that signatures are just created when instantiating the token, which is the moment that's actually needed.
We don't have the correct methods yet so it's not really helpful to have these here. We should add them back on v3.4 when features from v4.x get backported.
They're not helpful as well since functionality hasn't been ported from v4.0. We'll add them back on v3.4.
Adding references to which methods should be used instead
@MasterOdin can you please let me know if this solves the issue you raised? I don't want for this lib to annoy people with useless deprecation notes. |
Yeah, this looks like it would solve my issue in that there's a way to use non-deprecated functions for generating a token! 👍 One thing I noticed while looking through this is that the 3.3 release uses Builder::with while 4.0 uses Builder::withClaim. |
@MasterOdin well spotted! I'll fix it too. Thanks! |
@MasterOdin released 👍 |
Thanks so much! 👍 |
As pointed out by @MasterOdin in #133 we were a bit too eager to add the deprecation notes.
This solves that, allowing users to migrate in a smooth way.