-
Notifications
You must be signed in to change notification settings - Fork 374
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
change to signature of JWT.decode method #14
Comments
I don't believe it's intentional. I assume you'd expect the On Tue, Feb 12, 2013 at 10:02 AM, Rob Wygand notifications@github.comwrote:
Jeff Lindsay |
Yeah, that's what I figured... I just wanted to be sure of intent. I'll On Tue, Feb 12, 2013 at 12:26 PM, Jeff Lindsay notifications@github.comwrote:
|
Did you submit a patch for this? |
Yes, and it was merged: #16 |
Cool. |
JWT.decode can now, since the inclusion of MultiJson, raise a MultiJson::Decode error from lines 67 and 68. This means that he method signature of decode has changed to raise both JWT::DecodeError and MultiJson::DecodeError. Was this change intentional? It's breaking some test cases of mine that expect a JWT::DecodeError to be raised.
The text was updated successfully, but these errors were encountered: